Skip to contentSkip to conversation

devfs mysterious relabelling

DISCUSSION Russell Coker 2 participants 3 messages May 24, 2002 – May 28, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

On my systems I have devfsd do most of the device node labelling.

I have noticed that often the system_u:object_r:fixed_disk_device_t labels (for /dev/ide/host0/bus0/target0/lun0/*) will get changed to system_u:object_r:devfs_t (the default context for devfs).

It doesn't happen to the device node for the entire file system /dev/ide/host0/bus0/target0/lun0/disc and the device node /dev/ide/host0/bus0/target0/lun0/part5 (an extended partition).

I believe that this is not a user-land issue, and it's something in the kernel (but I have not proven this yet).

Also it seems to happen more often when under load (setfiles on the root file system usually does the job).

Signature · 9 lines
If you send email to me or to a mailing list that I use which has >4 lines
of legalistic junk at the end then you are specifically authorizing me to do
whatever I wish with the message and all other messages from your domain, by
posting the message you agree that your long legalistic sig is void.

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.
#1 lore raw
Quoted 10 lines · Russell Coker

On my systems I have devfsd do most of the device node labelling.

I have noticed that often the system_u:object_r:fixed_disk_device_t labels (for /dev/ide/host0/bus0/target0/lun0/*) will get changed to system_u:object_r:devfs_t (the default context for devfs).

It doesn't happen to the device node for the entire file system /dev/ide/host0/bus0/target0/lun0/disc and the device node /dev/ide/host0/bus0/target0/lun0/part5 (an extended partition).

Quoted 5 lines

I believe that this is not a user-land issue, and it's something in the kernel (but I have not proven this yet).

Also it seems to happen more often when under load (setfiles on the root file system usually does the job).

This could happen if a devfs entry is evicted from the dcache and is later looked up again, causing the security context to be re-acquired from the devfs_contexts configuration. Doesn't this issue also arise for the ownership and mode on devfs entries when they are managed by devfsd?

--
Stephen D. Smalley, NAI Labs
[email protected]

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#2 lore raw
Quoted 14 lines · Stephen Smalley
Quoted 13 lines · Russell Coker

On my systems I have devfsd do most of the device node labelling.

I have noticed that often the system_u:object_r:fixed_disk_device_t labels (for /dev/ide/host0/bus0/target0/lun0/*) will get changed to system_u:object_r:devfs_t (the default context for devfs).

It doesn't happen to the device node for the entire file system /dev/ide/host0/bus0/target0/lun0/disc and the device node /dev/ide/host0/bus0/target0/lun0/part5 (an extended partition).

I believe that this is not a user-land issue, and it's something in the kernel (but I have not proven this yet).

Quoted 7 lines
Quoted 2 lines

Also it seems to happen more often when under load (setfiles on the root file system usually does the job).

This could happen if a devfs entry is evicted from the dcache and is later looked up again, causing the security context to be re-acquired from the devfs_contexts configuration. Doesn't this issue also arise for the ownership and mode on devfs entries when they are managed by devfsd?

No! Devfs preserves the results of chmod/chown operations until the next reboot.

I'm surprised though, I thought that devfs entries would be locked in the dcache...

Signature · 9 lines
If you send email to me or to a mailing list that I use which has >4 lines
of legalistic junk at the end then you are specifically authorizing me to do
whatever I wish with the message and all other messages from your domain, by
posting the message you agree that your long legalistic sig is void.

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.