From: syzbot <syzbot+8073030e235a5a84dd31@syzkaller.appspotmail.com>
To: bfields@fieldses.org, boqun.feng@gmail.com, jlayton@kernel.org,
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: possible deadlock in f_getown
Date: Mon, 30 Nov 2020 11:23:07 -0800 [thread overview]
Message-ID: <0000000000009c212f05b557f00a@google.com> (raw)
In-Reply-To: <000000000000bf710a05b05ae3f6@google.com>
syzbot has bisected this issue to:
commit e918188611f073063415f40fae568fa4d86d9044
Author: Boqun Feng <boqun.feng@gmail.com>
Date: Fri Aug 7 07:42:20 2020 +0000
locking: More accurate annotations for read_lock()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=122fe51d500000
start commit: b6505459 Linux 5.10-rc6
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=112fe51d500000
console output: https://syzkaller.appspot.com/x/log.txt?x=162fe51d500000
kernel config: https://syzkaller.appspot.com/x/.config?x=b3a044ccf5b03ac4
dashboard link: https://syzkaller.appspot.com/bug?extid=8073030e235a5a84dd31
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11b43d79500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f2ed79500000
Reported-by: syzbot+8073030e235a5a84dd31@syzkaller.appspotmail.com
Fixes: e918188611f0 ("locking: More accurate annotations for read_lock()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-11-30 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 7:48 possible deadlock in f_getown syzbot
2020-11-30 12:39 ` syzbot
2020-11-30 19:23 ` syzbot [this message]
2021-09-23 6:03 ` [syzbot] " syzbot
2021-09-23 17:20 ` Desmond Cheong Zhi Xi
2021-09-23 17:54 ` Jeff Layton
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=0000000000009c212f05b557f00a@google.com \
--to=syzbot+8073030e235a5a84dd31@syzkaller.appspotmail.com \
--cc=bfields@fieldses.org \
--cc=boqun.feng@gmail.com \
--cc=jlayton@kernel.org \
--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.