[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <D20DBEF2.437A0%Shaun.Crampton@metaswitch.com>
Date: Thu, 3 Sep 2015 08:13:06 +0000
From: Shaun Crampton <Shaun.Crampton@...aswitch.com>
To: Daniel Borkmann <daniel@...earbox.net>
CC: Eric Dumazet <eric.dumazet@...il.com>,
Michael Marineau <michael.marineau@...eos.com>,
Chuck Ebbert <cebbert.lkml@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Peter White <Peter.White@...aswitch.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: ip_rcv_finish() NULL pointer and possibly related Oopses
>Looking at this one, I am still puzzeled where 0xffffffffa008772b and
>0xffffffffa008772b comes from ... some driver, bridge ...?
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?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists