Al Viro 1e2e547a93 do d_instantiate/unlock_new_inode combinations safely
For anything NFS-exported we do _not_ want to unlock new inode
before it has grown an alias; original set of fixes got the
ordering right, but missed the nasty complication in case of
lockdep being enabled - unlock_new_inode() does
	lockdep_annotate_inode_mutex_key(inode)
which can only be done before anyone gets a chance to touch
->i_mutex.  Unfortunately, flipping the order and doing
unlock_new_inode() before d_instantiate() opens a window when
mkdir can race with open-by-fhandle on a guessed fhandle, leading
to multiple aliases for a directory inode and all the breakage
that follows from that.

	Correct solution: a new primitive (d_instantiate_new())
combining these two in the right order - lockdep annotate, then
d_instantiate(), then the rest of unlock_new_inode().  All
combinations of d_instantiate() with unlock_new_inode() should
be converted to that.

Cc: stable@kernel.org	# 2.6.29 and later
Tested-by: Mike Marshall <hubcap@omnibond.com>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2018-05-11 15:36:37 -04:00
..
2006-10-02 09:55:27 -05:00
2008-05-13 08:22:10 -05:00
2016-03-30 10:48:28 -05:00
2013-06-29 12:56:42 +04:00
2013-06-05 14:47:19 -05:00
2006-10-02 09:55:27 -05:00
2017-04-19 14:21:23 +02:00
2017-04-19 14:21:23 +02:00
2017-04-19 14:21:23 +02:00
2007-04-26 07:30:29 -05:00
2011-03-31 11:26:23 -03:00
2013-06-05 14:47:19 -05:00
2016-09-06 12:17:24 -05:00
2006-10-02 09:55:27 -05:00
2006-10-02 09:55:27 -05:00
2017-02-09 11:57:22 -06:00