From: syzbot <syzbot+d2b6e8cc299748fecf25@syzkaller.appspotmail.com>
To: a@unstable.cc, b.a.t.m.a.n@lists.open-mesh.org,
davem@davemloft.net, dhowells@redhat.com, fweisbec@gmail.com,
ktkhai@virtuozzo.com, linux-afs@lists.infradead.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mareklindner@neomailbox.ch, miklos@szeredi.hu, mingo@kernel.org,
mszeredi@redhat.com, netdev@vger.kernel.org,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: Re: INFO: rcu detected stall in security_file_open (3)
Date: Thu, 29 Oct 2020 16:49:05 -0700 [thread overview]
Message-ID: <000000000000e0a53705b2d7ec44@google.com> (raw)
In-Reply-To: <000000000000bd1edd05b087535a@google.com>
syzbot suspects this issue was fixed by commit:
commit 1d0e850a49a5b56f8f3cb51e74a11e2fedb96be6
Author: David Howells <dhowells@redhat.com>
Date: Fri Oct 16 12:21:14 2020 +0000
afs: Fix cell removal
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14bc220a500000
start commit: fb0155a0 Merge tag 'nfs-for-5.9-3' of git://git.linux-nfs...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=41b736b7ce1b3ea4
dashboard link: https://syzkaller.appspot.com/bug?extid=d2b6e8cc299748fecf25
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1249c717900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1048d9e3900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: afs: Fix cell removal
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-10-29 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 12:49 INFO: rcu detected stall in security_file_open (3) syzbot
2020-10-29 23:49 ` syzbot [this message]
2020-11-06 11:40 ` David Howells
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=000000000000e0a53705b2d7ec44@google.com \
--to=syzbot+d2b6e8cc299748fecf25@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=fweisbec@gmail.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=miklos@szeredi.hu \
--cc=mingo@kernel.org \
--cc=mszeredi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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).