From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Borkmann Subject: Re: ip_rcv_finish() NULL pointer and possibly related Oopses Date: Thu, 03 Sep 2015 11:03:54 +0200 Message-ID: <55E80CFA.7050408@iogearbox.net> References: <20150826074959.48aea34c@as> <1440680401.8932.39.camel@edumazet-glaptop2.roam.corp.google.com> <55E7907D.9000606@iogearbox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Eric Dumazet , Michael Marineau , Chuck Ebbert , "linux-kernel@vger.kernel.org" , Peter White , "netdev@vger.kernel.org" To: Shaun Crampton Return-path: Received: from www62.your-server.de ([213.133.104.62]:60023 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750749AbbICJD6 (ORCPT ); Thu, 3 Sep 2015 05:03:58 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On 09/03/2015 10:13 AM, Shaun Crampton wrote: ... > Is there anything I can do on a running system to help figure this out? > Some sort of kernel equivalent to pmap to find out what module or device > owns that chunk of memory? Hmm, perhaps /proc/kallsyms could point to something. 0xffffffffa0087d81 and 0xffffffffa008772b could be from the same module, if any.