Thanks for the information. That's the Debian/Jessie kernel and it's years too late to get it fixed. Oh well at least it fails closed.
On 26 January 2017 12:22:35 am LHDT, Stephen Smalley <stephen.smalley@xxxxxxxxx> wrote:
>On Wed, Jan 25, 2017 at 1:22 AM, Russell Coker <russell@xxxxxxxxxxxx>
>wrote:
>> type=AVC msg=audit(1485258907.829:106): avc: denied { 0x800000 }
>for
>> pid=1280 comm="rewrite-0" name="after-the-deadline" dev="vda"
>ino=104107534
>> scontext=system_u:system_r:httpd_t:s0
>> tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=0
>>
>> I got the above after upgrading a system running kernel 3.16.0 to the
>latest
>> userspace. Why is this happening? Is this a bug?
>
>That would be a kernel bug; it means that you have a directory inode
>(for which that permission would be rmdir permission) that is wrongly
>assigned the file security class. Typically means that the filesystem
>did not set the file mode format bits before security_d_instantiate()
>was called.
>_______________________________________________
>Selinux mailing list
>Selinux@xxxxxxxxxxxxx
>To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx.
>To get help, send an email containing "help" to
>Selinux-request@xxxxxxxxxxxxx.
--
Sent from my Nexus 6P with K-9 Mail.
_______________________________________________
Selinux mailing list
Selinux@xxxxxxxxxxxxx
To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx.
To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
