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

From: Mike Snitzer
Date: Sun Nov 23 2014 - 23:10:55 EST

On Sun, Nov 23 2014 at 12:34pm -0500,
Eric Dumazet <eric.dumazet@xxxxxxxxx> wrote:

> From: Eric Dumazet <edumazet@xxxxxxxxxx>
> 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(), we are the last user of this mapped device, so can use
> the constant '1' instead of a lockdep_is_held(), not consistent with
> other uses of rcu_dereference_protected() which use md->suspend_lock
> mutex.
> Reported-by: Kirill A. Shutemov <kirill@xxxxxxxxxxxxx>
> Signed-off-by: Eric Dumazet <edumazet@xxxxxxxxxx>
> Fixes: 33423974bfc1 ("dm: Use rcu_dereference() for accessing rcu pointer")
> Cc: Pranith Kumar <bobby.prani@xxxxxxxxx>
> Cc: Mike Snitzer <snitzer@xxxxxxxxxx>

Thanks, I've staged this for 3.19:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at