Even in a (some sort of) fatal situation where SCardConnect never returns, it is better to scdaemon still works somehow.
This could be done if the feature ( T7401: PC/SC: Cancel SCardConnect with timeout) is implemented.
Before T7401 done, still, it would be possible only the connection which requests SCardConnect stops, but scdaemon itself still no hard lockup entirely.
| rG GnuPG | |||
| rG7b57539cf2c4 scd: No hard lock-up when apdu_connect never returns. | |||
| rG261a08566e38 scd: No hard lock-up when apdu_connect never returns. | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | • gniibe | T7396 Windows: hard lockup of scdaemon | ||
| Testing | • gniibe | T7402 No hard lockup when SCardConnect never returns |
In select_application function, we can minimize the holding W-lock.
Still, scanning the card reader list should be serialized, it's not needed keep holding the lock in the whole process.
A change is applied by: rG261a08566e38: scd: No hard lock-up when apdu_connect never returns.