diff options
author | Al Viro <viro@zeniv.linux.org.uk> | 2012-01-08 19:50:23 -0500 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2012-01-08 20:19:30 -0500 |
commit | 0ce8c0109f548ed75535d96ec5a347b410ed1472 (patch) | |
tree | c82c28de75da5b73c224cce18602d1a5680d27d7 /fs/isofs/inode.c | |
parent | da01636a6511c3bd0c1cf546c47b8e92a837a613 (diff) | |
download | linux-0ce8c0109f548ed75535d96ec5a347b410ed1472.tar.bz2 |
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>
Diffstat (limited to 'fs/isofs/inode.c')
0 files changed, 0 insertions, 0 deletions