Why not pass "vfsmount" to VFS functions?

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

 



Hello.

> > I guess the question is, why shouldn't a dentry object know what
> > vfsmount it belongs to is?  Can it belong to multiple vfsmount objects?
> > (Again, probably showing my igornance here).
> 
> If you have the same tree mounted in two places, they'll have
> different vfsmounts.

That makes auditing difficult.
Recently, the importance of saving operation log is increasing,
and it is convenient to log it using d_path().
But due to "bind mount" functionality, it is impossible to
uniquely determine which pathname was requested.
It would be nice if VFS functions receive not only "dentry"
but also "vfsmount" parameter so that auditing functions can
easily calculate the requested pathname.
-
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

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux