[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1441282243.8932.219.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Thu, 03 Sep 2015 05:10:43 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Shaun Crampton <Shaun.Crampton@...aswitch.com>
Cc: Daniel Borkmann <daniel@...earbox.net>,
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
On Thu, 2015-09-03 at 10:09 +0000, 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.
>
> Any good: https://transfer.sh/szGRE/kallsyms ?
>
seems to be cryptd module.
Have you tried to run an pristine upstream kernel ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists