[pkg-gnupg-maint] Bug#992415: Bug#992415: pinentry-tty: Segfault as host is entering S3/S0ix

[Daniel Kahn Gillmor]

Control: tags 992415 + moreinfo unreproducible

Hi Andrew--

On Wed 2021-08-18 19:15:22 +0930, Andrew Savchenko wrote:
> After issuing `systemctl suspend`, pinentry segfaults with the following
> output in the dmesg:
>
> ```
> kern  :info  : [Aug18 21:14] pinentry-tty[140518]: segfault at 0 ip
> 00007f395bd5a217 sp 00007ffe29e70310 error 4 in
>
> libc-2.31.so[7f395bd0b000+14b000] kern  :info  : [  +0.000011] Code: 89
> 23 85 c0 75 d4 e9 2b ff ff ff 0f 1f 84 00 00 00 00 00 e8 3b ad 00 00 e9
> f9 fe ff ff e8 11 94 09 00 90 41 54 55 48 89 fd 53 <8b> 07 f6 c4 20 0f
> 85 ee 00 00 00 89 c2 81 e2 00 80 00 00 0f 84 ed
> ```

I tried to replicate this under qemu on debian unstable with pinentry
1.1.0-4 and did not see the behavior you're describing.

Here's what I did:

 - launch a debian x86_64 qemu/kvm-based guest 

 - as a non-privileged user, connected to it via ssh, ran "pinentry-tty"
   -- in that console, i typed "getpin" (got a prompt "PIN: ")

 - while waiting on that prompt, as the superuser, i did "systemctl
   suspend"

 - the qemu guest froze, and from its monitor port, i ran
   "system_wakeup"

 - the system unfroze, and i was able to continue entering my PIN, and
   pinentry-tty behaved as expected.

 - there was nothing in the dmesg to indicate any problem.

Are you able to help replicate this?

    --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/attachments/20220428/8e2fa2a3/attachment.sig>