All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	linux-kernel@vger.kernel.org, davem@davemloft.net,
	netdev@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>,
	Pravin B Shelar <pshelar@nicira.com>
Subject: Re: NULL pointer dereference when loading the gre module (3.10.0-rc4)
Date: Fri, 7 Jun 2013 20:34:38 +0200	[thread overview]
Message-ID: <20130607183438.GA23064@uio.no> (raw)
In-Reply-To: <1370629568.9844.87.camel@gandalf.local.home>

On Fri, Jun 07, 2013 at 02:26:08PM -0400, Steven Rostedt wrote:
> On Fri, 2013-06-07 at 19:52 +0200, Steinar H. Gunderson wrote:
> Ah, that's because of this: module_init(ipgre_init);  Where it makes it
> into:
> 
> 00000000 <init_module>:
>    0:   55                      push   %ebp
>    1:   89 e5                   mov    %esp,%ebp
>    3:   53                      push   %ebx
>    4:   83 ec 08                sub    $0x8,%esp
>    7:   c7 04 24 00 00 00 00    movl   $0x0,(%esp)
>                         a: R_386_32     .rodata.str1.4
> 
> We can use ipgre_tap_init_net, and the offset of 0xb032 (45106) as that
> was 0xffffffffa0e5d034 - 0xffffffffa0e52002. Do you have CONFIG_NET_NS
> set?

ipgre_tap_init_net is 000000000000001a, but there's no way I can subtract
0xb053 from that? Sorry, I'm confused. :-)

> You can also cat /proc/modules. It gives you where the modules are
> located.

I've booted back to 3.9.x already; I couldn't live with a crashing kernel like
that. Unfortunately it's not that easy for me to reboot this machine all the
time either. :-/

/* Steinar */
-- 
Homepage: http://www.sesse.net/

  reply	other threads:[~2013-06-07 18:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 22:16 NULL pointer dereference when loading the gre module (3.10.0-rc4) Steinar H. Gunderson
2013-06-07  3:06 ` Steven Rostedt
2013-06-07  3:59   ` Eric Dumazet
2013-06-07  8:31     ` Steinar H. Gunderson
2013-06-13 10:01     ` David Miller
2013-06-07  8:27   ` Steinar H. Gunderson
2013-06-07  8:43   ` Steinar H. Gunderson
2013-06-07  8:54   ` Steinar H. Gunderson
2013-06-07 13:40     ` Eric Dumazet
2013-06-07 15:15       ` Steven Rostedt
2013-06-07 15:46         ` Steinar H. Gunderson
2013-06-07 16:12           ` Steven Rostedt
2013-06-07 17:52             ` Steinar H. Gunderson
2013-06-07 18:26               ` Steven Rostedt
2013-06-07 18:34                 ` Steinar H. Gunderson [this message]
2013-06-07 18:44                   ` Steven Rostedt
2013-06-07 18:46                     ` Steinar H. Gunderson
2013-06-07 20:26                       ` Eric Dumazet

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=20130607183438.GA23064@uio.no \
    --to=sgunderson@bigfoot.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.com \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.au \
    /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.