public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsa@cumulusnetworks.com>
To: Richard Alpe <richard.alpe@ericsson.com>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	James Morris <jmorris@namei.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-next] oops in ip_route_input_noref
Date: Wed, 16 Sep 2015 07:07:42 -0600	[thread overview]
Message-ID: <55F9699E.5080807@cumulusnetworks.com> (raw)
In-Reply-To: <55F9578C.40209@ericsson.com>

On 9/16/15 5:50 AM, Richard Alpe wrote:
> On 2015-09-16 11:24, Sergey Senozhatsky wrote:
>> Hi,
>>
>> 4.3.0-rc1-next-20150916
>>
>> oops after removal of rndis usb device

Hi Sergey:

Is this with KVM or baremetal?

-----8<-----
thanks for the analysis

>> addr2line -e vmlinux -i 0xffffffff8146c0b1
>> net/ipv4/route.c:1815
>> net/ipv4/route.c:1905
>>
>>
>> which seems to be this line ip_route_input_noref()->ip_route_input_slow():
>> ...
>> 1813         rth->rt_is_input = 1;
>> 1814         if (res.table)
>> 1815                 rth->rt_table_id = res.table->tb_id;
>> 1816
>> ...
>>
>>
>> added by b7503e0cdb5dbec5d201aa69d8888c14679b5ae8
>>
>>      net: Add FIB table id to rtable
>>
>>      Add the FIB table id to rtable to make the information available for
>>      IPv4 as it is for IPv6.
>>
>>
>> 	-ss

Hi Richard:

> I to get an Oops in ip_route_input_noref(). It happens occasionally during bootup.
> KVM environment using virtio driver. Let me know if you need any additional info or
> if you want me to try to bisect it.
>
> Starting network...
> ...
> [    0.877040] BUG: unable to handle kernel NULL pointer dereference at 0000000000000056
> [    0.877597] IP: [<ffffffff8155b5e2>] ip_route_input_noref+0x1a2/0xb00

Can you send me your kernel config and qemu command line? KVM with 
virtio networking is a primary test vehicle, and I did not encounter 
this at all.

Thanks,
David



  reply	other threads:[~2015-09-16 13:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  9:24 [linux-next] oops in ip_route_input_noref Sergey Senozhatsky
2015-09-16 11:50 ` Richard Alpe
2015-09-16 13:07   ` David Ahern [this message]
2015-09-16 13:53     ` Richard Alpe
2015-09-16 13:57       ` David Ahern
2015-09-16 14:08         ` Richard Alpe
2015-09-16 13:59       ` Richard Alpe
2015-09-16 14:00         ` David Ahern
2015-09-16 23:47     ` Sergey Senozhatsky
2015-09-17  7:26       ` Tomeu Vizoso
2015-09-16 13:24 ` David Ahern
2015-09-16 15:00 ` Fabio Estevam
2015-09-16 15:04   ` David Ahern
2015-09-17  8:58     ` Thierry Reding
2015-09-18 23:06       ` Andrew Morton
2015-09-19 14:34         ` David Ahern

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=55F9699E.5080807@cumulusnetworks.com \
    --to=dsa@cumulusnetworks.com \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richard.alpe@ericsson.com \
    --cc=sergey.senozhatsky.work@gmail.com \
    /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