All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaun Crampton <Shaun.Crampton@metaswitch.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Michael Marineau <michael.marineau@coreos.com>,
	Chuck Ebbert <cebbert.lkml@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Peter White <Peter.White@metaswitch.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: ip_rcv_finish() NULL pointer and possibly related Oopses
Date: Fri, 4 Sep 2015 14:57:10 +0000	[thread overview]
Message-ID: <D20F6FAC.43BD1%Shaun.Crampton@metaswitch.com> (raw)
In-Reply-To: <1441282243.8932.219.camel@edumazet-glaptop2.roam.corp.google.com>



On 03/09/2015 13:10, "Eric Dumazet" <eric.dumazet@gmail.com> wrote:

>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 ?

No, I haven't tried that; I'm not sure if it's feasible with CoreOS.


      reply	other threads:[~2015-09-04 14:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26  8:46 ip_rcv_finish() NULL pointer and possibly related Oopses Shaun Crampton
2015-08-26 11:49 ` Chuck Ebbert
2015-08-26 13:01   ` Shaun Crampton
2015-08-26 20:54   ` Michael Marineau
2015-08-27 13:00     ` Eric Dumazet
2015-08-27 16:16       ` Michael Marineau
2015-08-27 16:30         ` Eric Dumazet
2015-08-27 16:32           ` Michael Marineau
2015-08-27 16:40         ` David Miller
2015-08-27 16:47           ` Michael Marineau
2015-09-02 16:39       ` Shaun Crampton
2015-09-03  0:12         ` Daniel Borkmann
2015-09-03  8:13           ` Shaun Crampton
2015-09-03  9:03             ` Daniel Borkmann
2015-09-03 10:09               ` Shaun Crampton
2015-09-03 12:10                 ` Eric Dumazet
2015-09-04 14:57                   ` Shaun Crampton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D20F6FAC.43BD1%Shaun.Crampton@metaswitch.com \
    --to=shaun.crampton@metaswitch.com \
    --cc=Peter.White@metaswitch.com \
    --cc=cebbert.lkml@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.marineau@coreos.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.