Al Viro a8b0026847 rename(): avoid a deadlock in the case of parents having no common ancestor ... ... 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>		2023-11-25 02:54:14 -05:00
..
client	Sixteen smb3/cifs client fixes	2023-11-11 17:17:22 -08:00
common	Add definition for new smb3.1.1 command type	2023-10-30 09:57:03 -05:00
server	rename(): avoid a deadlock in the case of parents having no common ancestor	2023-11-25 02:54:14 -05:00
Kconfig
Makefile