From: syzbot <syzbot+d7b7f1412c02134efa6d@syzkaller.appspotmail.com>
To: amcohen@nvidia.com, axboe@fb.com,
bridge@lists.linux-foundation.org, davem@davemloft.net,
dsahern@kernel.org, edumazet@google.com, hch@lst.de,
hdanton@sina.com, idosch@nvidia.com, ivecera@redhat.com,
jiri@resnulli.us, kbusch@kernel.org, kuba@kernel.org,
lengchao@huawei.com, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, llvm@lists.linux.dev,
nathan@kernel.org, ndesaulniers@google.com,
netdev@vger.kernel.org, pabeni@redhat.com, razor@blackwall.org,
roopa@nvidia.com, sagi@grimberg.me,
syzkaller-bugs@googlegroups.com, trix@redhat.com
Subject: Re: [syzbot] [bridge?] possible deadlock in br_multicast_rcv (3)
Date: Mon, 02 Oct 2023 06:08:29 -0700 [thread overview]
Message-ID: <0000000000006ba21a0606bb78f9@google.com> (raw)
In-Reply-To: <000000000000c4c9d405f2643e01@google.com>
syzbot has bisected this issue to:
commit 0ae3eb7b4611207e140e9772398b9f88b72d6839
Author: Amit Cohen <amcohen@nvidia.com>
Date: Mon Feb 1 19:47:49 2021 +0000
netdevsim: fib: Perform the route programming in a non-atomic context
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13afdae6680000
start commit: 2faac9a98f01 Merge tag 'keys-fixes-20230321' of git://git...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=106fdae6680000
console output: https://syzkaller.appspot.com/x/log.txt?x=17afdae6680000
kernel config: https://syzkaller.appspot.com/x/.config?x=aaa4b45720ca0519
dashboard link: https://syzkaller.appspot.com/bug?extid=d7b7f1412c02134efa6d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14aea34ec80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13001e91c80000
Reported-by: syzbot+d7b7f1412c02134efa6d@syzkaller.appspotmail.com
Fixes: 0ae3eb7b4611 ("netdevsim: fib: Perform the route programming in a non-atomic context")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-10-02 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 16:40 [syzbot] possible deadlock in br_multicast_rcv (3) syzbot
2023-10-02 13:08 ` syzbot [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=0000000000006ba21a0606bb78f9@google.com \
--to=syzbot+d7b7f1412c02134efa6d@syzkaller.appspotmail.com \
--cc=amcohen@nvidia.com \
--cc=axboe@fb.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=hch@lst.de \
--cc=hdanton@sina.com \
--cc=idosch@nvidia.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kbusch@kernel.org \
--cc=kuba@kernel.org \
--cc=lengchao@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=sagi@grimberg.me \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.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;
as well as URLs for NNTP newsgroup(s).