netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: James Morris <jmorris@namei.org>
Cc: netdev@vger.kernel.org, Curtis Doty <Curtis@GreenKey.net>
Subject: Re: oops in net/ipv4/icmp.c:icmp_send() with icmp_errors_use_inbound_ifaddr (fwd)
Date: Mon, 14 May 2007 20:46:29 +0200	[thread overview]
Message-ID: <4648AE85.6020608@trash.net> (raw)
In-Reply-To: <Line.LNX.4.64.0705141430120.8521@d.namei>

James Morris wrote:
> ---------- Forwarded message ----------
> Date: Mon, 14 May 2007 08:15:50 -0700 (PDT)
> From: Curtis Doty <Curtis@GreenKey.net>
> To: Linux Kernel <linux-kernel@vger.kernel.org>
> Subject: oops in net/ipv4/icmp.c:icmp_send() with icmp_errors_use_inbound_ifaddr
> 
> Summary: On a multi-homed box, after turning on
> /proc/sys/net/ipv4/icmp_errors_use_inbound_ifaddr, it now periodically oopses
> when trying to lookup the source address to use for sending an ICMP in response
> to a jump ipt_REJECT.
> 
> I'm still trying to figure out what makes this test case unique. It spuriously
> occurs with many fedora builds of 2.6.{18,19,20} all of which don't appear to
> have any patches in this area of the kernel. Just _maybe_ it's because of a
> combination of dogleg routing and overloading one vlan with multiple subnets:
> 
> [..]
> 
> BUG: unable to handle kernel NULL pointer dereference at virtual address
> 000000a8
> [...]
> EIP is at inet_select_addr+0x4/0x9f
> eax: 00000000   ebx: f8b97046   ecx: 000000fd   edx: 00000000
> esi: 000000fd   edi: 00000001   ebp: f71cd0ac   esp: c078bc9c
> ds: 007b   es: 007b   ss: 0068
> Process swapper (pid: 0, ti=c078b000 task=c06fc480 task.ti=c0746000)
> Stack: f8b97046 f601b130 c05fd0b6 f728b980 f728b980 f8b5adbb c05bcb6e c078bd74
>        00000003 00000003 00000246 00000246 00000000 f887e014 f8a611a6 f7c1ea80
>        f728b9a8 00000000 f727d220 f887e000 00000001 00000072 f7383800 f728b980
> Call Trace:
>  [<f8b97046>] reject+0x0/0x4ae [ipt_REJECT]
>  [<c05fd0b6>] icmp_send+0x14d/0x39b


A REJECT target in the output chain will trigger this in combination
with icmp_errors_use_inbound_ifaddr because skb->dev is still NULL
at this point and its passed to inet_select_addr.

I'll look into this.

  reply	other threads:[~2007-05-14 18:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14 18:30 oops in net/ipv4/icmp.c:icmp_send() with icmp_errors_use_inbound_ifaddr (fwd) James Morris
2007-05-14 18:46 ` Patrick McHardy [this message]
2007-05-14 19:19   ` Patrick McHardy
2007-05-17 16:52     ` Patrick McHardy
2007-05-18  0:57       ` Julian Anastasov
2007-05-19 21:50       ` David Miller
2007-05-21 17:03         ` Patrick McHardy
2007-05-20  5:26     ` Herbert Xu
2007-05-21 16:36       ` Patrick McHardy
2007-05-21 21:28         ` Herbert Xu
2007-05-21 21:32           ` Patrick McHardy
2007-05-14 20:24   ` Curtis Doty

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=4648AE85.6020608@trash.net \
    --to=kaber@trash.net \
    --cc=Curtis@GreenKey.net \
    --cc=jmorris@namei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).