Files
i2som-imx-linux/include/linux
Al Viro d7065da038 get rid of the magic around f_count in aio
__aio_put_req() plays sick games with file refcount.  What
it wants is fput() from atomic context; it's almost always
done with f_count > 1, so they only have to deal with delayed
work in rare cases when their reference happens to be the
last one.  Current code decrements f_count and if it hasn't
hit 0, everything is fine.  Otherwise it keeps a pointer
to struct file (with zero f_count!) around and has delayed
work do __fput() on it.

Better way to do it: use atomic_long_add_unless( , -1, 1)
instead of !atomic_long_dec_and_test().  IOW, decrement it
only if it's not the last reference, leave refcount alone
if it was.  And use normal fput() in delayed work.

I've made that atomic_long_add_unless call a new helper -
fput_atomic().  Drops a reference to file if it's safe to
do in atomic (i.e. if that's not the last one), tells if
it had been able to do that.  aio.c converted to it, __fput()
use is gone.  req->ki_file *always* contributes to refcount
now.  And __fput() became static.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-05-27 22:03:07 -04:00
..
2010-05-17 22:39:48 -07:00
2010-05-14 17:08:01 -04:00
2010-05-27 09:12:53 -07:00
2010-05-19 13:38:54 -04:00
2010-05-17 16:30:58 -07:00
2010-05-21 19:30:44 +02:00
2010-05-25 08:07:01 -07:00
2010-05-27 09:12:42 -07:00
2010-05-21 09:34:29 -07:00
2010-05-21 09:37:29 -07:00
2010-05-14 15:09:32 -04:00
2010-05-17 12:17:10 +03:00
2010-05-17 05:27:42 +02:00
2010-05-19 13:44:27 +10:00
2010-05-21 19:30:44 +02:00
2010-05-27 09:12:50 -07:00
2010-05-27 09:12:51 -07:00
2010-05-25 11:41:43 -04:00
2010-05-17 17:18:50 -07:00
2010-05-27 09:12:43 -07:00
2010-05-15 23:28:39 -07:00
2010-05-21 09:34:29 -07:00
2010-05-19 22:15:46 +09:30