All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaun Crampton <Shaun.Crampton@metaswitch.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Peter White <Peter.White@metaswitch.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Chuck Ebbert <cebbert.lkml@gmail.com>
Subject: Re: ip_rcv_finish() NULL pointer and possibly related Oopses
Date: Wed, 26 Aug 2015 13:01:12 +0000	[thread overview]
Message-ID: <D2037365.41362%Shaun.Crampton@metaswitch.com> (raw)
In-Reply-To: <20150826074959.48aea34c@as>


>And the kernel thinks it's
>outside of any normal text section, so it does not try to dump any
>code from before the instruction pointer.
>
>   0:	48 8b 88 40 03 00 00 	mov    0x340(%rax),%rcx
>   7:	e8 1d dd dd ff       	callq  0xffffffffffdddd29
>   c:	5d                   	pop    %rbp
>   d:	c3                   	retq
>
>Did you write your own module loader or something?

We certainly didn't but CoreOS may have.  I've asked CoreOS if they know
what's going on.

Are there any extra diagnostics I can gather from a CoreOS system to help
figure out what's going on there?  Is there anything I can do to get more
useful diagnostics when one of these failures occur?  As noted, I can
reproduce the issue but it's expensive, requiring hundreds of VMs to
hammer away for an hour or so.


  reply	other threads:[~2015-08-26 13:01 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 [this message]
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

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=D2037365.41362%Shaun.Crampton@metaswitch.com \
    --to=shaun.crampton@metaswitch.com \
    --cc=Peter.White@metaswitch.com \
    --cc=cebbert.lkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.