From: Yonghong Song <yhs@fb.com>
To: David Ahern <dsahern@gmail.com>, netdev <netdev@vger.kernel.org>,
Alexei Starovoitov <ast@fb.com>, Martin Lau <kafai@fb.com>,
Dave Jones <dsj@fb.com>
Subject: Re: oops with ip6_rt_cache_alloc
Date: Sun, 26 Aug 2018 21:57:40 -0700 [thread overview]
Message-ID: <4f7ab12f-37c2-5bdc-5993-be8da71ec0de@fb.com> (raw)
In-Reply-To: <2314c9c2-27ab-c470-5e8a-4e28e53810b2@gmail.com>
On 8/24/18 4:04 PM, David Ahern wrote:
> On 8/24/18 4:26 PM, Yonghong Song wrote:
>> Hi,
>>
>> We got a kernel oops with the following stack trace:
>>
>> CPU: 24 PID: 0 Comm: swapper/24 Not tainted
>> 4.16.0-10_fbk1_1183_g7e4ee4c8171c #10
>> "Hardware name: Quanta Leopard-DDR3/Leopard-DDR3, BIOS F06_3A16.DDR3
>> 11/19/2015"
>> RIP: 0010:ip6_rt_get_dev_rcu+0x6/0x60
>> RSP: 0018:ffff88046fb03c78 EFLAGS: 00010286
>> RAX: 0000000040000003 RBX: ffff88035a6c1500 RCX: ffffffff81ec5dc0
>> RDX: ffff88033192a090 RSI: ffff88033192a0a0 RDI: 0000000000000000
>
> RDI = 0 means the rt passed to ip6_rt_get_dev_rcu is NULL. I believe
> that can't happen prior to the fib6_info changes. After the fib6_info
> changes, it means the 'from' is NULL and that is not expected.
>
> ...
>
>> Our internal experiments showed that an early version of 4.16 works fine
>> and after backporting some ipv6 route related changes and the above
>> problem showed up.
>
> Can you run the test on 4.18?
We will give a try with 4.18. Thanks.
prev parent reply other threads:[~2018-08-27 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 22:26 oops with ip6_rt_cache_alloc Yonghong Song
2018-08-24 23:04 ` David Ahern
2018-08-27 4:57 ` Yonghong Song [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=4f7ab12f-37c2-5bdc-5993-be8da71ec0de@fb.com \
--to=yhs@fb.com \
--cc=ast@fb.com \
--cc=dsahern@gmail.com \
--cc=dsj@fb.com \
--cc=kafai@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox