From: syzbot <syzbot+36baa6c2180e959e19b1@syzkaller.appspotmail.com>
To: aia21@cantab.net, bvanassche@acm.org, dvyukov@google.com,
gaoxiang25@huawei.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
miaoxie@huawei.com, mingo@kernel.org, mingo@redhat.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk, will@kernel.org
Subject: Re: WARNING: bad unlock balance in rcu_core
Date: Mon, 04 May 2020 00:05:04 -0700 [thread overview]
Message-ID: <00000000000076622305a4cd26ae@google.com> (raw)
In-Reply-To: <000000000000c0bffa0586795098@google.com>
syzbot suspects this bug was fixed by commit:
commit 10476e6304222ced7df9b3d5fb0a043b3c2a1ad8
Author: Peter Zijlstra <peterz@infradead.org>
Date: Fri Mar 13 08:56:38 2020 +0000
locking/lockdep: Fix bad recursion pattern
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=142baee4100000
start commit: 5a1e843c Merge tag 'mips_fixes_5.4_3' of git://git.kernel...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=420126a10fdda0f1
dashboard link: https://syzkaller.appspot.com/bug?extid=36baa6c2180e959e19b1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1108239ce00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13cf40a8e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: locking/lockdep: Fix bad recursion pattern
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-05-04 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 8:28 WARNING: bad unlock balance in rcu_core syzbot
2019-10-16 9:27 ` syzbot
2019-10-16 10:01 ` Gao Xiang
2020-02-27 15:18 ` Dmitry Vyukov
2020-03-02 4:39 ` Bart Van Assche
2020-05-04 7:05 ` 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=00000000000076622305a4cd26ae@google.com \
--to=syzbot+36baa6c2180e959e19b1@syzkaller.appspotmail.com \
--cc=aia21@cantab.net \
--cc=bvanassche@acm.org \
--cc=dvyukov@google.com \
--cc=gaoxiang25@huawei.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).