From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: Re: [PATCH 1/2] genl: Fix genl dumpit() locking. Date: Fri, 23 Aug 2013 11:51:25 +0200 Message-ID: <1377251485.14021.17.camel@jlt4.sipsolutions.net> References: <1377143882-20717-1-git-send-email-pshelar@nicira.com> <1377156980.14110.16.camel@jlt4.sipsolutions.net> <1377193906.14110.27.camel@jlt4.sipsolutions.net> <1377195534.14110.29.camel@jlt4.sipsolutions.net> <1377242982.14021.8.camel@jlt4.sipsolutions.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: netdev , Jesse Gross To: Pravin Shelar Return-path: Received: from s3.sipsolutions.net ([144.76.43.152]:38450 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755003Ab3HWJv3 (ORCPT ); Fri, 23 Aug 2013 05:51:29 -0400 In-Reply-To: <1377242982.14021.8.camel@jlt4.sipsolutions.net> Sender: netdev-owner@vger.kernel.org List-ID: On Fri, 2013-08-23 at 09:29 +0200, Johannes Berg wrote: > > You are thinking abt genl-sock -> nlk -> cb_lock which is not used in > > genl-dump locking if cb_lock is NULL while creating nl socket. > > You're right, this is also done for each userland socket, so each socket > now gets its own cb_mutex. This would help genl families with > parallel_ops. I'm still missing something. Kernel 3.4 had cb_mutex assign to the genl_mutex, but we saw the original crash there, apparently dumpit *wasn't* (always) locked with it? johannes