From: syzbot <syzbot+3e12e14ee01b675e1af2@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 kill_fasync
Date: Tue, 17 Nov 2020 15:19:10 -0800 [thread overview]
Message-ID: <000000000000e2437705b455b8bb@google.com> (raw)
In-Reply-To: <0000000000009c775805b0c1b811@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=10b46429500000
start commit: 7c8ca812 Add linux-next specific files for 20201117
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=12b46429500000
console output: https://syzkaller.appspot.com/x/log.txt?x=14b46429500000
kernel config: https://syzkaller.appspot.com/x/.config?x=ff4bc71371dc5b13
dashboard link: https://syzkaller.appspot.com/bug?extid=3e12e14ee01b675e1af2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14b1dba6500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12de8636500000
Reported-by: syzbot+3e12e14ee01b675e1af2@syzkaller.appspotmail.com
Fixes: e918188611f0 ("locking: More accurate annotations for read_lock()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-11-17 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 10:29 possible deadlock in kill_fasync syzbot
2020-11-17 20:32 ` syzbot
2020-11-17 23:19 ` 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=000000000000e2437705b455b8bb@google.com \
--to=syzbot+3e12e14ee01b675e1af2@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.