Re: [PATCH librados2-perl] do not shut down the handle twice if a signal arrives at exit

[Maximiliano Sandoval <m.sandoval@proxmox.com>]

Kefu Chai <k.chai@proxmox.com> writes:

> When a pveceph worker finishes, the CLI sends SIGTERM to its process
> group, which includes the pverados child. That child is often already
> shutting down the handle after seeing EOF, so the handler then calls
> rados_shutdown() on the freed handle and the child segfaults.
>
> The handlers outlived the eval anyway, as the 'local' only covered
> $SIG{HUP}. So ignore the signals before shutting down, and install the
> handlers first thing in the child.
>
> Signed-off-by: Kefu Chai <k.chai@proxmox.com>
> ---
>  PVE/RADOS.pm | 19 ++++++++++++-------
>  1 file changed, 12 insertions(+), 7 deletions(-)
> [..]

I ran into this today when trying to create a EC pool and allocating an
image on a freshly installed PVE 9 3-node cluster with the latest
packages via:

pveceph pool create test-ec --erasure-coding k=4,m=2
pvesm alloc test-ec 999 vm-999-disk-0 1G

The pool creation succeeds and the alloc times out, one can see in the
journal:

Oct 20 14:45:33 c3-pve-201 kernel: pverados[2811]: segfault at 3b40 ip 00007d006bd44ba0 sp 00007ffd43e96c28 error 4 in libc.so.6[95ba0,7d006bcd7000+163000] likely on CPU 1 (core 1, socket 0)
Oct 20 14:45:33 c3-pve-201 kernel: Code: 00 e8 64 27 fa ff 48 8d 0d ed 9c 11 00 ba c2 01 00 00 48 8d 35 47 13 11 00 48 8d 3d 55 13 11 00 e8 45 27 fa ff 0f 1f 44 00 00 <8b> 47 10 89 c2 81 e2 7f 01 00 00 83 e0 7c 0f 85 ac 00 00 00 53 48

and the health status will be stuck "Reduced data availability" in.

One thing that would be good to have in the commit message is what
setups were affected and since when, if this is a regression.

-- 
Maximiliano