mirror of
https://github.com/torvalds/linux
synced 2024-10-06 11:25:23 +00:00
a8b0026847
... and fix the directory locking documentation and proof of correctness. Holding ->s_vfs_rename_mutex *almost* prevents ->d_parent changes; the case where we really don't want it is splicing the root of disconnected tree to somewhere. In other words, ->s_vfs_rename_mutex is sufficient to stabilize "X is an ancestor of Y" only if X and Y are already in the same tree. Otherwise it can go from false to true, and one can construct a deadlock on that. Make lock_two_directories() report an error in such case and update the callers of lock_rename()/lock_rename_child() to handle such errors. And yes, such conditions are not impossible to create ;-/ Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> |
||
---|---|---|
.. | ||
copy_up.c | ||
dir.c | ||
export.c | ||
file.c | ||
inode.c | ||
Kconfig | ||
Makefile | ||
namei.c | ||
overlayfs.h | ||
ovl_entry.h | ||
params.c | ||
params.h | ||
readdir.c | ||
super.c | ||
util.c | ||
xattrs.c |