* Casey Schaufler (casey@xxxxxxxxxxxxxxxx) wrote: > > They are being posted now as a request for comment. > > Presently the AppArmor > > code - being a user of the LSM interface - does not > > receive the vfsmount > > correspoding to an operation and has to employ > > convoluted and slow mechanisms > > in an attempt to determine the vfsmount which are > > error prone. > > Would it be possible for you to describe those > methods? Perhaps there is a better way to go > about getting the information you need without > introducing this level of change. It's not really worth describing, since it's not acceptable in upstream. But it basically cycles vfsmnts and looks for matches to guess which part of the tree the dentry is in. This kind of change (or perhaps straight to struct path) is definitely needed from AA. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
