From: syzbot <syzbot+7ee926c5e237e614ccb1@syzkaller.appspotmail.com>
To: bp@alien8.de, davem@davemloft.net, dhowells@redhat.com,
fweisbec@gmail.com, herbert@gondor.apana.org.au, hpa@zytor.com,
linux-afs@lists.infradead.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@kernel.org, mingo@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: INFO: rcu detected stall in sys_open (2)
Date: Wed, 16 Dec 2020 05:40:03 -0800 [thread overview]
Message-ID: <0000000000002aca3d05b69503ac@google.com> (raw)
In-Reply-To: <000000000000f683660598300559@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=128ceadf500000
start commit: c85fb28b Merge tag 'arm64-fixes' of git://git.kernel.org/p..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=de7f697da23057c7
dashboard link: https://syzkaller.appspot.com/bug?extid=7ee926c5e237e614ccb1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1227c177900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13553f60500000
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-12-16 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 18:35 INFO: rcu detected stall in sys_open (2) syzbot
2020-12-16 13:40 ` syzbot [this message]
2020-12-17 8:18 ` Dmitry Vyukov
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=0000000000002aca3d05b69503ac@google.com \
--to=syzbot+7ee926c5e237e614ccb1@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=fweisbec@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@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).