Re: setfiles crashing when SELinux is disabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Jul 30, 2017 at 8:52 PM, Laurent Bigonville <bigon@xxxxxxxxxx> wrote:
> Hi,
>
> When using sefiles (setfiles -m -F -v
> /etc/selinux/refpolicy/contexts/files/file_contexts.bin  /) when SELinux is
> disabled, it crahes with the fillowing trace:
>
> #0  __strcmp_sse2_unaligned () at
> ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31
> No locals.
> #1  0x00007f13241957be in restorecon_sb (pathname=0xd36aa93160
> "/usr/include/xf86drm.h", flags=flags@entry=0x7fffd3700ae3, sb=<optimized
> out>, sb=<optimized out>) at selinux_restorecon.c:666
>         newcon = 0xd36abdc100 "system_u:object_r:usr_t:s0"
>         curcon = 0x0
>         newtypecon = 0x0
>         rc = <optimized out>
>         updated = false
>         lookup_path = <optimized out>
> #2  0x00007f1324196810 in selinux_restorecon
> (pathname_orig=pathname_orig@entry=0xd36aa943e0 "/",
> restorecon_flags=<optimized out>) at selinux_restorecon.c:984

Having "curcon = 0x0" with a non-NULL newcon in selinux_restorecon.c
looks like the bug fixed by commit a9094fae2c7b ("libselinux: avoid
calling strcmp() on a NULL pointer",
https://github.com/SELinuxProject/selinux/commit/a9094fae2c7bcd14af7263f9bb7fbacff5bc761c).
Which version are you using? Does back-porting this commit fix your
issue?

Thanks,
Nicolas




[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux