From: syzbot <syzbot+f9545ab3e9f85cd43a3a@syzkaller.appspotmail.com>
To: ebiggers@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.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_lock_release
Date: Wed, 29 Apr 2020 23:15:02 -0700 [thread overview]
Message-ID: <00000000000033365905a47bfcd4@google.com> (raw)
In-Reply-To: <000000000000fdd3f3058bfcf369@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=16d64bac100000
start commit: 7d194c21 Linux 5.4-rc4
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=6c03e4d33fa96d51
dashboard link: https://syzkaller.appspot.com/bug?extid=f9545ab3e9f85cd43a3a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10a0a8c0e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13dd2dd8e00000
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-04-30 6:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 12:37 WARNING: bad unlock balance in rcu_lock_release syzbot
2019-10-13 21:28 ` syzbot
2019-10-15 7:56 ` Jan Kara
2019-10-17 5:27 ` Eric Biggers
2020-04-30 6:15 ` 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=00000000000033365905a47bfcd4@google.com \
--to=syzbot+f9545ab3e9f85cd43a3a@syzkaller.appspotmail.com \
--cc=ebiggers@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.