Re: [PATCH ] drivers/md: use proper rcu accessor

2014-11-23 Thread Mike Snitzer
On Sun, Nov 23 2014 at 12:31pm -0500, Eric Dumazet wrote: > On Sun, 2014-11-23 at 11:53 -0500, Mike Snitzer wrote: > > On Sun, Nov 23, 2014 at 11:40 AM, Eric Dumazet > > wrote: > > > From: Eric Dumazet > > > > > > rcu_dereference() should be used in sections protected by rcu_read_lock. > > > >

Re: [PATCH ] drivers/md: use proper rcu accessor

2014-11-23 Thread Eric Dumazet
On Sun, 2014-11-23 at 11:53 -0500, Mike Snitzer wrote: > On Sun, Nov 23, 2014 at 11:40 AM, Eric Dumazet wrote: > > From: Eric Dumazet > > > > rcu_dereference() should be used in sections protected by rcu_read_lock. > > > > For writers, holding some kind of mutex or lock, > > rcu_dereference_prote

Re: [PATCH ] drivers/md: use proper rcu accessor

2014-11-23 Thread Mike Snitzer
On Sun, Nov 23, 2014 at 11:40 AM, Eric Dumazet wrote: > From: Eric Dumazet > > rcu_dereference() should be used in sections protected by rcu_read_lock. > > For writers, holding some kind of mutex or lock, > rcu_dereference_protected() is the way to go, adding explicit lockdep > bits. > > In __unb

[PATCH ] drivers/md: use proper rcu accessor

2014-11-23 Thread Eric Dumazet
From: Eric Dumazet rcu_dereference() should be used in sections protected by rcu_read_lock. For writers, holding some kind of mutex or lock, rcu_dereference_protected() is the way to go, adding explicit lockdep bits. In __unbind(), although there is no mutex or lock held, we are about to free t