FS#74936 - [gssproxy/krb5] dumps core after update

Attached to Project: Arch Linux
Opened by Tarqi Kazan (Tarqi) - Wednesday, 01 June 2022, 20:12 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 06 June 2022, 10:16 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Andreas Radke (AndyRTR)
Levente Polyak (anthraxx)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

Updated linux and gssproxy in one pacman session. gssproxy starts but dumps core after starting, sometimes at once, sometimes after a few minutes.

Additional info:
* linux 5.18.1.arch1-1
* gssproxy 0.9.0-1

Steps to reproduce:
Update to above packages and try to run the usual nfs-service

Coredump;

gssproxy[7552]: free(): invalid pointer
systemd[1]: Started Process Core Dump (PID 7959/UID 0).
systemd-coredump[7960]: [🡕] Process 7552 (gssproxy) of user 0 dumped core.
Module linux-vdso.so.1 with build-id 4bbdd9447359021631434950a65998efe247ea02
Module libgpg-error.so.0 with build-id f9aaa96d5ddf6f6872051ed7abcdfe6bdaff9b1c
Module libm.so.6 with build-id 210ec9905e41825671210f8f7d0b24d6c371196a
Module libbasicobjects.so.0 with build-id 6e1239a4f9ee182d7e069de144ef1246dc5eb689
Module libpath_utils.so.1 with build-id 0beb448fbd423aff523062e6af75b7e46353673d
Module libcollection.so.4 with build-id a730b9664f23306904c661f9bf17b8d7a48ab439
Module ld-linux-x86-64.so.2 with build-id fc93487393eea02b5bc6e76e48976fc325294c24
Module libgcc_s.so.1 with build-id 0e3de903950e35ae59a5de8c00b1817a4a71ca01
Module liblz4.so.1 with build-id e63600ab23b2f6997f42fac2fa56e1f02ce159a1
Module libzstd.so.1 with build-id 3bccb8fe08e48d5ea135b1d0f99de0d771dd752f
Module liblzma.so.5 with build-id 28b40c7af8098a66af6ee093b6986b91cad7694d
Module libgcrypt.so.20 with build-id 8bf3cb884124273640de797a3e77d86c98434ea4
Module libcap.so.2 with build-id 21b00ab76bb16fde56fd741f07233c78069f0579
Module libresolv.so.2 with build-id 89a368a6ad1b392d126a2a5beb9c2f61ade00279
Module libkeyutils.so.1 with build-id ac405ddd17be10ce538da3211415ee50c8f8df79
Module libkrb5support.so.0 with build-id 36db7c21bc57a9b934ad2d3463782db9fef4af07
Module libcom_err.so.2 with build-id 358b783c9b3d12ba8248519ea2e7f3da4c4e0297
Module libc.so.6 with build-id 388993b6ef62f964bc7bf473c069fbfe957b9e44
Module libgssapi_krb5.so.2 with build-id 1813217c8baf82a1078772eed0d868310cd59f8b
Module libgssrpc.so.4 with build-id 2f698ca2909f5bfb5897787451d53a9a1b208067
Module libverto.so.0 with build-id c1fde8755561dd8087e818317957630a112d3538
Module libini_config.so.5 with build-id 48f11fa19b2fe5a7117a57dbe11c9c4228999e41
Module libref_array.so.1 with build-id 1b0d2c72a002af0d4343de2b8e6a39f1807a8018
Module libsystemd.so.0 with build-id 385f15b287d5a2f1952983f0230859f47291fea8
Module libpopt.so.0 with build-id 069e16aec5a44daff896aa3c50cc035148362fd6
Module libk5crypto.so.3 with build-id f1c113fea46023cdf62c7e51cb643c45831abdd5
Module libkrb5.so.3 with build-id 9350783c946d77aec8ee8fd9c6bc12f4f7b72be9
Module gssproxy with build-id 49709edd2114187c9820ba836b2b905558eb5de7
Stack trace of thread 7552:
#0 0x00007f95f6c8e36c n/a (libc.so.6 + 0x8e36c)
#1 0x00007f95f6c3e838 raise (libc.so.6 + 0x3e838)
#2 0x00007f95f6c28535 abort (libc.so.6 + 0x28535)
#3 0x00007f95f6c8245e n/a (libc.so.6 + 0x8245e)
#4 0x00007f95f6c980cc n/a (libc.so.6 + 0x980cc)
#5 0x00007f95f6c99f6c n/a (libc.so.6 + 0x99f6c)
#6 0x00007f95f6c9c8f3 free (libc.so.6 + 0x9c8f3)
#7 0x00007f95f6feb3c2 verto_cleanup (libverto.so.0 + 0x53c2)
#8 0x00005590344f5b69 n/a (gssproxy + 0x5b69)
#9 0x00007f95f6c29290 n/a (libc.so.6 + 0x29290)
#10 0x00007f95f6c2934a __libc_start_main (libc.so.6 + 0x2934a)
#11 0x00005590344f6855 n/a (gssproxy + 0x6855)
ELF object binary architecture: AMD x86-64
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Monday, 06 June 2022, 10:16 GMT
Reason for closing:  Fixed
Additional comments about closing:  initial issue fixed in 0.9.1
Comment by loqs (loqs) - Wednesday, 01 June 2022, 20:28 GMT
Have you looked at  FS#72750 
Comment by Tarqi Kazan (Tarqi) - Wednesday, 01 June 2022, 20:42 GMT
Nice catch, I searched for gssproxy in the bugtracker and did not find anything. However, this worked until the update and there is nothing I can do, I think this should be handled by the core developers, as it is a system package and a dependency of nfs-utils. But I'm open to a discussion :)
Comment by loqs (loqs) - Thursday, 02 June 2022, 10:15 GMT
There has been a fix in libverto that might be related [1]. You could try rebuilding krb5 with that patch applied [2] and see if you can still reproduce the issue.

[1] https://github.com/latchset/libverto/commit/e145d317b0026677b7626770a1630667c00ad409
[2] PKGBUILD.diff
Comment by Mantas MikulÄ—nas (grawity) - Saturday, 04 June 2022, 10:01 GMT
According to the upstream developers, Arch should be packaging libverto as a standalone library to avoid this issue:

https://github.com/gssapi/gssproxy/issues/36#issuecomment-921137677

(However, `debug_level` revealed that this is not the entire problem – a bigger issue is that gssproxy now deliberately tries to exit when idle; crashes are just a side effect.)
Comment by loqs (loqs) - Sunday, 05 June 2022, 02:32 GMT
Please try the attached patch, which is intended to disable the timeout when not using socket based activation.
Edit:
Upstream fix https://github.com/gssapi/gssproxy/pull/57/commits/7acb54f78f2cbc90d5ca6421e69cdfc8dbd4b2ac
Comment by Lee Donaghy (deadite66) - Sunday, 05 June 2022, 06:35 GMT
been just over an hour with a patched gssproxy and no core dump.
Comment by Andreas Radke (AndyRTR) - Sunday, 05 June 2022, 19:02 GMT
Please test new 0.9.1 release.
Comment by Lee Donaghy (deadite66) - Sunday, 05 June 2022, 20:13 GMT
same again with 0.9.1, just over an hour and no core dump.
Comment by Tarqi Kazan (Tarqi) - Sunday, 05 June 2022, 20:23 GMT
@deadit66: If you stop the service, will it still crash?

See also https://bugs.archlinux.org/task/72750#comment208771
Comment by Lee Donaghy (deadite66) - Sunday, 05 June 2022, 20:54 GMT
yes is crashed.

Jun 05 21:53:44 Plasma systemd[1]: Stopping GSSAPI Proxy Daemon...
Jun 05 21:53:44 Plasma gssproxy[3720253]: free(): invalid pointer
Jun 05 21:53:44 Plasma systemd[1]: gssproxy.service: Main process exited, code=dumped, status=6/ABRT
Jun 05 21:53:44 Plasma systemd[1]: gssproxy.service: Failed with result 'core-dump'.
Jun 05 21:53:44 Plasma systemd[1]: Stopped GSSAPI Proxy Daemon.
Comment by Andreas Radke (AndyRTR) - Monday, 06 June 2022, 09:57 GMT
The exit crash seems to be a different bug. Is upstream already are of that one?
Comment by Mantas MikulÄ—nas (grawity) - Monday, 06 June 2022, 10:06 GMT
They're aware (the crashes are not new) – that's the already mentioned  FS#72750  and https://github.com/gssapi/gssproxy/issues/36.

Loading...