Thread (12 messages) flat view 12 messages, 2 authors, 2013-08-26

Re: [PATCH 1/2] genl: Fix genl dumpit() locking.

From: Johannes Berg <johannes@sipsolutions.net>
Date: 2013-08-22 07:36:25

On Wed, 2013-08-21 at 20:58 -0700, Pravin B Shelar wrote:
In case of genl-family with parallel ops off, dumpif() callback
is expected to run under genl_lock, But commit def3117493eafd9df
(genl: Allow concurrent genl callbacks.) changed this behaviour
where only first dumpit() op was called under genl-lock.
For subsequent dump, only nlk->cb_lock was taken.
Following patch fixes it by defining locked dumpit() and done()
callback which takes care of genl-locking.
As I've commented over in the other thread, I really think this is the
wrong thing to do. It was never the case that dumpit() was actually
locked under genl_lock(), and adding it doesn't really help anyone.

johannes
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help