From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+3f2db34df769d77edf8c@syzkaller.appspotmail.com>
Cc: "David Howells" <dhowells@redhat.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
linux-afs@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: INFO: rcu detected stall in __se_sys_mount
Date: Tue, 8 Dec 2020 07:33:01 +0100 [thread overview]
Message-ID: <CACT4Y+aX1eZ3Pwb=LfeH+rsadx2ehwmfFb9MQy=FK25MegP6CA@mail.gmail.com> (raw)
In-Reply-To: <00000000000013d25705b5e55be6@google.com>
On Mon, Dec 7, 2020 at 9:06 PM syzbot
<syzbot+3f2db34df769d77edf8c@syzkaller.appspotmail.com> wrote:
>
> 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=162cebcf500000
> 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=3f2db34df769d77edf8c
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11df5d4f900000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=157851e0500000
>
> 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
#syz fix: afs: Fix cell removal
prev parent reply other threads:[~2020-12-08 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 15:42 INFO: rcu detected stall in __se_sys_mount syzbot
2020-10-08 12:15 ` syzbot
2020-12-07 20:06 ` syzbot
2020-12-08 6:33 ` Dmitry Vyukov [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='CACT4Y+aX1eZ3Pwb=LfeH+rsadx2ehwmfFb9MQy=FK25MegP6CA@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=dhowells@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=syzbot+3f2db34df769d77edf8c@syzkaller.appspotmail.com \
--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).