login
Header Space

 
 

Re: [AppArmor 19/45] Add struct vfsmount parameters to vfs_rename()

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Al Viro <viro@...>
Cc: <jjohansen@...>, <akpm@...>, <linux-kernel@...>, <linux-security-module@...>, Tony Jones <tonyj@...>, Andreas Gruenbacher <agruen@...>
Date: Friday, October 26, 2007 - 2:23 pm

On Fri, Oct 26, 2007 at 08:37:49AM +0100, Al Viro wrote:
te
g...

In the current code, both vfsmounts are always identical, and so one of
the two should go, agreed.

The thought behind passing both vfsmounts was that they could differ but
point to the same super_block, in which case renames would still be
possible at least from a filesystem point of view. The essential
restriction here is that both files must be on the same device; the vfs
restriction of not allowing cross-mount renames is arbitrary.
Cross-mount renames are not allowed currently, and granted, they may not
be very useful, either.


As always, it's a pleasure to see the genuine Viro charm at play.
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [AppArmor 19/45] Add struct vfsmount parameters to vfs_r..., John Johansen, (Fri Oct 26, 2:23 pm)
speck-geostationary