[lkml]   [2019]   [Jan]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFD] A mount api that notices previous mounts (Eric W. Biederman) writes:

> Casey Schaufler <> writes:
>> Are you taking the LSM specific mount options into account?
> In the design yes, and I allow setting them. It appears in the code
> to retrieve the mount options I forgot to call security_sb_show_options.
> For finding the super block that you are going to mount the LSM mount
> options are not relevant. Even nfs will not want to set those early as
> they do not help determine the nfs super block. So the only place where
> there is anything interesting in my api is in reading back the security
> options so they can be compared to the options the mounter is setting.
> I will add the missing call to security_sb_show_options which is enough
> to fix selinux. Unfortunately smack does not currently implement
> .sb_show_options. Not implementing smack_sb_show_options means
> /proc/mounts fails to match /etc/mtab which is a bug and it is likely
> a real workd bug for the people who use smack and don't want to depend
> on /etc/mtab, or are transitioning away from it.
> Casey do you want to implement smack_sb_show_options or should I put it
> on my todo list?

Oh. I should add that I am always parsing the LSM mount options out so
that there is not a chance of the individual filesystems implementing
comflicting options even when there are no LSMs active. Without that I
am afraid we run the risk of having LSM mount otions in conflict with
ordinary filesystems options at some point and by the time we discover
it it would start introducing filesystem regressions.

That does help with stack though as there is no fundamental reason only
one LSM could process mount options.


 \ /
  Last update: 2019-01-30 03:01    [W:0.080 / U:12.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site