From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755074AbaIBSkd (ORCPT ); Tue, 2 Sep 2014 14:40:33 -0400 Received: from mail-lb0-f177.google.com ([209.85.217.177]:56384 "EHLO mail-lb0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755051AbaIBSkb (ORCPT ); Tue, 2 Sep 2014 14:40:31 -0400 MIME-Version: 1.0 In-Reply-To: <1409681914.978561.162800349.5A7FA784@webmail.messagingengine.com> References: <20140829195339.GA9780@kria> <1409363489.2980.17.camel@localhost> <1409680684.972417.162793869.03CF8A61@webmail.messagingengine.com> <1409681914.978561.162800349.5A7FA784@webmail.messagingengine.com> Date: Tue, 2 Sep 2014 11:40:30 -0700 Message-ID: Subject: Re: RTNL: assertion failed at net/ipv6/addrconf.c (1699) From: Cong Wang To: Hannes Frederic Sowa Cc: Sabrina Dubroca , Tommi Rantala , "David S. Miller" , Alexey Kuznetsov , James Morris , Hideaki YOSHIFUJI , Patrick McHardy , netdev , LKML , trinity@vger.kernel.org, Dave Jones Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 2, 2014 at 11:18 AM, Hannes Frederic Sowa wrote: > Those ASSERT_RTNLs were misplaced and only caught the callers mostly > from addrconf.c. I don't mind getting reports from stable kernel users > and fixing those, too (or help fixing those). ASSERT_RTNL is not > dangerous. > > We had a long history in not correctly using rtnl lock in ipv6/multicast > code and those wrongfully placed ASSERT_RTNLs were my bad when I fixed > the duplicate address detection handling. > > If enough multicast addresses are subscribed to an interface we might > again get those splats because enabling promisc mode on an interface > will also check for rtnl lock. > Sure, I never doubt adding ASSERT_RTNL() is helpful, I just still think this should be for net-next, or at least a separated patch. I don't want my patch to be blamed in others' "Fixes:". :)