search for: urand_fd

On 11/2/18 2:46 PM, Jeremy Allison via samba wrote: > the abort(), which gets triggered if urand_fd == -1 > after open. So you'll need to debug that. Correct. The gdb output I pasted was during the abort. Gdb is showing urand_fd is not -1.

On 11/2/18 1:32 PM, Jeremy Allison wrote: > What errno is being returned on open of /dev/urandom ? I think the backtrace is being munged or the stack is being blown. When I debug during the crash here is what I find: (gdb) p urand_fd $4 = 56 OK... so the fd is set? and 56? I can confirm that fd 56 is /dev/urandom: $ ls -l /proc/14777/fd/56 lr-x------. 1 michael michael 64 Nov  2 14:17 /proc/14777/fd/56 -> /dev/urandom So for grins what is the errno? (gdb) p errno $5 = 95  -- EOPNOTSUPP I'm not sure that helped.

On 11/2/18 4:28 PM, Jeremy Allison wrote: > if you're getting the abort(), then urand_fd == -1. > If urand_fd != -1 and you're hitting the abort then > you have a compiler bug. A compiler bug is also possible. When I have time I'll try to rebuild Samba with -O0 to make sure it isn't an optimization issue.

Hi, I maintain Kodi[1] in RPMFusion[2] and the latest version of Kodi, 18.0, is crashing when trying to browse the SMB network. The previous version, 17.x, worked fine. The backtrace shows that Samba was not able to open /dev/urandom, which can't be true and must be masking another issue. The issue occurs on any Fedora 28 or 29 system (multiple user reports[3]). SELinux is disabled and