[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 09 Sep 2020 06:19:06 -0700
From: syzbot <syzbot+22e87cdf94021b984aa6@...kaller.appspotmail.com>
To: bfields@...ldses.org, boqun.feng@...il.com, jlayton@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
mingo@...hat.com, peterz@...radead.org,
syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk,
will@...nel.org
Subject: Re: WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected (2)
syzbot has bisected this issue to:
commit f08e3888574d490b31481eef6d84c61bedba7a47
Author: Boqun Feng <boqun.feng@...il.com>
Date: Fri Aug 7 07:42:30 2020 +0000
lockdep: Fix recursive read lock related safe->unsafe detection
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13034be1900000
start commit: dff9f829 Add linux-next specific files for 20200908
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10834be1900000
console output: https://syzkaller.appspot.com/x/log.txt?x=17034be1900000
kernel config: https://syzkaller.appspot.com/x/.config?x=37b3426c77bda44c
dashboard link: https://syzkaller.appspot.com/bug?extid=22e87cdf94021b984aa6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=108b740d900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12daa9ed900000
Reported-by: syzbot+22e87cdf94021b984aa6@...kaller.appspotmail.com
Fixes: f08e3888574d ("lockdep: Fix recursive read lock related safe->unsafe detection")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Powered by blists - more mailing lists