Al Viro 0ce8c0109f ext[34]: avoid i_nlink warnings triggered by drop_nlink/inc_nlink kludge in symlink()
Both ext3 and ext4 put the half-created symlink inode into the orphan list
for a while (see the comment in ext[34]_symlink() for gory details).  Then,
if everything went fine, they pull it out of the orphan list and bump the
link count back to 1.  The thing is, inc_nlink() is going to complain about
seeing somebody changing i_nlink from 0 to 1.  With a good reason, since
normally something like that is a bug.  Explicit set_nlink(inode, 1) does
the same thing as inc_nlink() here, but it does *not* complain - exactly
because it should be usable in strange situations like this one.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2012-01-08 20:19:30 -05:00
..
2011-07-25 14:30:23 -04:00
2007-10-17 08:42:47 -07:00
2012-01-03 22:54:58 -05:00
2012-01-03 22:52:40 -05:00
2010-07-23 12:50:55 +02:00
2005-10-30 17:37:25 -08:00
2011-03-31 11:26:23 -03:00
2010-05-21 18:31:19 -04:00
2010-05-21 18:31:19 -04:00