[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0000000000006ba21a0606bb78f9@google.com>
Date: Mon, 02 Oct 2023 06:08:29 -0700
From: syzbot <syzbot+d7b7f1412c02134efa6d@...kaller.appspotmail.com>
To: amcohen@...dia.com, axboe@...com, bridge@...ts.linux-foundation.org,
davem@...emloft.net, dsahern@...nel.org, edumazet@...gle.com, hch@....de,
hdanton@...a.com, idosch@...dia.com, ivecera@...hat.com, jiri@...nulli.us,
kbusch@...nel.org, kuba@...nel.org, lengchao@...wei.com,
linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org,
llvm@...ts.linux.dev, nathan@...nel.org, ndesaulniers@...gle.com,
netdev@...r.kernel.org, pabeni@...hat.com, razor@...ckwall.org,
roopa@...dia.com, sagi@...mberg.me, syzkaller-bugs@...glegroups.com,
trix@...hat.com
Subject: Re: [syzbot] [bridge?] possible deadlock in br_multicast_rcv (3)
syzbot has bisected this issue to:
commit 0ae3eb7b4611207e140e9772398b9f88b72d6839
Author: Amit Cohen <amcohen@...dia.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@...kaller.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
Powered by blists - more mailing lists