From: syzbot <syzbot+1a14a0f8ce1a06d4415f@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,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mareklindner@neomailbox.ch,
mike.kravetz@oracle.com, mingo@kernel.org,
netdev@vger.kernel.org, sw@simonwunderlich.de,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
viro@zeniv.linux.org.uk
Subject: Re: INFO: rcu detected stall in exit_group
Date: Mon, 09 Nov 2020 03:03:05 -0800 [thread overview]
Message-ID: <000000000000b4227e05b3aa8101@google.com> (raw)
In-Reply-To: <000000000000a48f9e05aef6cce1@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=14b65c3a500000
start commit: 34d4ddd3 Merge tag 'linux-kselftest-5.9-rc5' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a9075b36a6ae26c9
dashboard link: https://syzkaller.appspot.com/bug?extid=1a14a0f8ce1a06d4415f
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10c6642d900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=132d00fd900000
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-11-09 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 14:58 syzbot
2020-11-09 11:03 ` syzbot [this message]
2020-11-11 11:12 ` 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=000000000000b4227e05b3aa8101@google.com \
--to=syzbot+1a14a0f8ce1a06d4415f@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=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mareklindner@neomailbox.ch \
--cc=mike.kravetz@oracle.com \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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