Unsure if it is a samba bug, but it should not crash.
Steps to reproduce:
* Base 7.3 install
* yum install samba-winbind
* edit /etc/nsswitch.conf to show the following host line:
hosts: files wins dns myhostname
* systemctl start winbind
* ping redhat.com
"Quick fix" could be to have /usr/lib64/samba/ in
The proper fix would likely to fix libnss_wins.so.2
link. Please let me know if the bug should be reassigned
$ ldd /lib64/libnss_wins.so.2
linux-vdso.so.1 => (0x00007ffefcf2d000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f683cd2a000)
libwbclient.so.0 => /lib64/libwbclient.so.0 (0x00007f683cb1b000)
libreplace-samba4.so => not found
libc.so.6 => /lib64/libc.so.6 (0x00007f683c759000)
libwinbind-client-samba4.so => /usr/lib64/samba/libwinbind-client-samba4.so (0x00007f683c555000)
libreplace-samba4.so => /usr/lib64/samba/libreplace-samba4.so (0x00007f683c351000)
This is both a Samba bug (wrong search path/DSO location) and glibc bug (we should report and error and not crash).
This is fixed upstream. The fix involves some ld.so cleanup, but should be backportable.
The first upstream bug (16628) will be fixed in Red Hat Enterprise Linux 8. The second bug still needs to be fixed upstream.
*** Bug 1500128 has been marked as a duplicate of this bug. ***
Created attachment 1643297 [details]
The last three patches still await upstream review.
Upstream testing revealed that the fix is incomplete. We need to backport the fix for this bug as well: https://sourceware.org/bugzilla/show_bug.cgi?id=25396
(In reply to Florian Weimer from comment #18)
> Upstream testing revealed that the fix is incomplete. We need to backport
> the fix for this bug as well:
These fixes are included in glibc-2.28-101.el8.
ok. updating the doc_text_flag to +.
Verified with elf/tst-dlopen-nodelete-reloc, elf/tst-initfinilazyfail,
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.