From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shaun Crampton Subject: Re: ip_rcv_finish() NULL pointer and possibly related Oopses Date: Thu, 3 Sep 2015 10:09:09 +0000 Message-ID: References: <20150826074959.48aea34c@as> <1440680401.8932.39.camel@edumazet-glaptop2.roam.corp.google.com> <55E7907D.9000606@iogearbox.net> <55E80CFA.7050408@iogearbox.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT Cc: Eric Dumazet , Michael Marineau , Chuck Ebbert , "linux-kernel@vger.kernel.org" , Peter White , "netdev@vger.kernel.org" To: Daniel Borkmann Return-path: In-Reply-To: <55E80CFA.7050408@iogearbox.net> Content-Language: en-US Content-ID: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org >... >> 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. Any good: https://transfer.sh/szGRE/kallsyms ?