Re: [PATCH net-next-2.6] fasync: RCU locking

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Lai Jiangshan
Date: Wednesday, April 14, 2010 - 1:36 am

Eric Dumazet wrote:

Since rcu_read_lock() protects fasync_struct *fa for us, we can access
to @fa safely even fasync_remove_entry() is just called.

But this patch does not ensure 'fa->fa_file is not freed' nor
'fa->fa_fd is not released', so kill_fasync_rcu() may do wrong thing
if there is no other code ensure it.
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH net-next-2.6] fasync: RCU locking, Eric Dumazet, (Wed Apr 14, 12:42 am)
Re: [PATCH net-next-2.6] fasync: RCU locking, Lai Jiangshan, (Wed Apr 14, 1:36 am)
Re: [PATCH net-next-2.6] fasync: RCU locking, Eric Dumazet, (Wed Apr 14, 7:57 am)
Re: [PATCH net-next-2.6] fasync: RCU locking, Eric Dumazet, (Wed Apr 14, 8:34 am)
Re: [PATCH net-next-2.6] fasync: RCU locking, Paul E. McKenney, (Wed Apr 14, 8:41 am)
Re: [PATCH net-next-2.6] fasync: RCU locking, David Miller, (Wed Apr 21, 4:19 pm)