From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Ahern Subject: Re: IPv6 issue in next-20171102 - lockdep and BUG handling RA packet. Date: Tue, 7 Nov 2017 09:29:25 +0900 Message-ID: <51f7ccd1-6c80-d902-1a19-b885b5f88c24@gmail.com> References: <15801.1510001814@turing-police.cc.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org To: valdis.kletnieks@vt.edu, "David S. Miller" , Eric Dumazet Return-path: In-Reply-To: <15801.1510001814@turing-police.cc.vt.edu> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 11/7/17 5:56 AM, valdis.kletnieks@vt.edu wrote: > I've hit this 6 times now, across 3 boots: > > Nov 3 11:04:54 turing-police kernel: [ 547.814748] BUG: sleeping function called from invalid context at mm/slab.h:422 > > Nov 3 20:24:11 turing-police kernel: [ 60.093793] BUG: sleeping function called from invalid context at mm/slab.h:422 > Nov 4 20:20:54 turing-police kernel: [86264.366955] BUG: sleeping function called from invalid context at mm/slab.h:422 > Nov 5 19:17:40 turing-police kernel: [172469.769179] BUG: sleeping function called from invalid context at mm/slab.h:422 > Nov 6 06:07:37 turing-police kernel: [211467.239460] BUG: sleeping function called from invalid context at mm/slab.h:422 > > Nov 6 14:12:43 turing-police kernel: [ 54.891848] BUG: sleeping function called from invalid context at mm/slab.h:422 > > Something seems to be going astray while handling a RA packet. Odd. I tested RA before sending the patches and again just now - no traceback with an RCU / lock debugging kernel. What is sending the RA's in your case? I'd like to understand the config and add a test for this.