From: Jakub Kicinski <kuba@kernel.org>
To: syzbot <syzbot+eaaf6c4a6a8cb1869d86@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, gregkh@linuxfoundation.org,
keescook@chromium.org, ktkhai@virtuozzo.com,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pombredanne@nexb.com,
stephen@networkplumber.org, syzkaller-bugs@googlegroups.com,
tom@herbertland.com, yoshfuji@linux-ipv6.org
Subject: Re: inconsistent lock state in ila_xlat_nl_cmd_add_mapping
Date: Tue, 29 Dec 2020 17:37:30 -0800 [thread overview]
Message-ID: <20201229173730.65f74253@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <000000000000b14d8c05735dcdf8@google.com>
On Mon, 13 Aug 2018 21:40:03 -0700 syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 78cbac647e61 Merge branch 'ip-faster-in-order-IP-fragments'
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=14df4828400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=9100338df26ab75
> dashboard link: https://syzkaller.appspot.com/bug?extid=eaaf6c4a6a8cb1869d86
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=13069ad2400000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+eaaf6c4a6a8cb1869d86@syzkaller.appspotmail.com
#syz invalid
Hard to track down what fixed this, but the lockdep splat is mixing up
locks from two different hashtables, so there was never a real issue
here.
next prev parent reply other threads:[~2020-12-30 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 4:40 inconsistent lock state in ila_xlat_nl_cmd_add_mapping syzbot
2020-12-30 1:37 ` Jakub Kicinski [this message]
2020-12-30 1:52 ` Cong Wang
2020-12-30 2:16 ` Jakub Kicinski
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=20201229173730.65f74253@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=ktkhai@virtuozzo.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=stephen@networkplumber.org \
--cc=syzbot+eaaf6c4a6a8cb1869d86@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tom@herbertland.com \
--cc=yoshfuji@linux-ipv6.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).