Hide Forgot
Description of problem: rpc.gssd segfaults upon first user login with nfs-utils-1.2.3-15. Reverting to nfs-utils-1.2.3-7 fixes the problem. Seriously, why is nfs-utils turning into such a crap shoot lately? Do you have any kerberized nfs4 test systems?? RHEL 6.1 released with broken nfs-utils for kerberized nfsv4 and hasn't been fixed in the meantime, and now you're pushing broken shit back to 6.0. Yes, this is a rant. Yes, your engineering and QA sucks. Version-Release number of selected component (if applicable): # rpm -qa | grep nfs-utils nfs-utils-1.2.3-15.el6.x86_64 nfs-utils-lib-1.1.5-1.el6.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Install this update. 2. Try and log in with users home directories mounted over nfs4 with Kerberos. 3. rpc.gssd segfaults. Actual results: rpc.gssd[10864]: segfault at ffffffffffff0eb0 ip 00007fa6f10761fc sp 00007fffeae30cf0 error 4 in libc-2.12.so[7fa6f1001000+197000] abrt-hook-ccpp[10973]: segfault at 8 ip 000000306787f9c1 sp 00007fffef5d0988 error 4 in libc-2.12.so[3067800000+197000] Expected results: Additional info:
That should be: "Reverting to nfs-utils-1.2.2-7 fixes the problem. "
A backtrace: (gdb) run -f -vvv Starting program: /usr/sbin/rpc.gssd -f -vvv [Thread debugging using libthread_db enabled] beginning poll Program received signal SIG37, Real-time event 37. 0x00007ffff674e018 in __poll (fds=0x7ffff8206650, nfds=256, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:83 83 return INLINE_SYSCALL (poll, 3, CHECK_N (fds, nfds), nfds, timeout); Missing separate debuginfos, use: debuginfo-install keyutils-libs-1.4-1.el6.x86_64 libselinux-2.0.94-2.el6.x86_64 (gdb) bt #0 0x00007ffff674e018 in __poll (fds=0x7ffff8206650, nfds=256, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:83 #1 0x00007ffff7ff31c8 in gssd_run () at gssd_main_loop.c:224 #2 0x00007ffff7ff2ede in main (argc=<value optimized out>, argv=<value optimized out>) at gssd.c:187
Well, what can I say... I couldn't agree more with the rant above.
(In reply to comment #4) > Well, what can I say... I couldn't agree more with the rant above. My apologies for you pain... Obviously if we saw something like this in our QE testing it would have been fixed... Question, Are you using a Windows AD as you KDC?
This bz seems to be similar: https://bugzilla.redhat.com/show_bug.cgi?id=751353
Nope, the KDC is another RH6 box. I should add I am seeing this on sc ientific linux boxes, but will go and see if I can reproduce it on RHEL boxes. BZ #765909 also seems relevant, perhaps. However, I have not disabled ipv6 anywhere.
OK, I can't reproduce this at all on a RHEL6 box, so it seems to be an issue with the rebuilt SL package. Many apologies for the noise (and misplaced rant).