summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEric Dumazet <dada1@cosmosbay.com>2008-12-10 18:35:45 +0100
committerAl Viro <viro@zeniv.linux.org.uk>2009-01-01 00:07:42 +0100
commitfd659fd6275d3426d7967da1f0e3638bbbd2fedb (patch)
tree0c499f1c63a18d1dd8e70b278ad59c00262f21a8
parentmake INIT_FS use the __RW_LOCK_UNLOCKED initialization (diff)
downloadlinux-fd659fd6275d3426d7967da1f0e3638bbbd2fedb.tar.xz
linux-fd659fd6275d3426d7967da1f0e3638bbbd2fedb.zip
fix f_count description in Documentation/filesystems/files.txt
Documentation/filesystems/files.txt was not updated when f_count became an atomic_long_t. atomic_long_inc_not_zero() is now used instead of atomic_inc_not_zero() Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
-rw-r--r--Documentation/filesystems/files.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/filesystems/files.txt b/Documentation/filesystems/files.txt
index bb0142f61084..ac2facc50d2a 100644
--- a/Documentation/filesystems/files.txt
+++ b/Documentation/filesystems/files.txt
@@ -76,13 +76,13 @@ the fdtable structure -
5. Handling of the file structures is special. Since the look-up
of the fd (fget()/fget_light()) are lock-free, it is possible
that look-up may race with the last put() operation on the
- file structure. This is avoided using atomic_inc_not_zero()
+ file structure. This is avoided using atomic_long_inc_not_zero()
on ->f_count :
rcu_read_lock();
file = fcheck_files(files, fd);
if (file) {
- if (atomic_inc_not_zero(&file->f_count))
+ if (atomic_long_inc_not_zero(&file->f_count))
*fput_needed = 1;
else
/* Didn't get the reference, someone's freed */
@@ -92,7 +92,7 @@ the fdtable structure -
....
return file;
- atomic_inc_not_zero() detects if refcounts is already zero or
+ atomic_long_inc_not_zero() detects if refcounts is already zero or
goes to zero during increment. If it does, we fail
fget()/fget_light().