From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+2a89b1fb6539ff150c16@syzkaller.appspotmail.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: INFO: rcu detected stall in do_swap_page
Date: Wed, 11 Nov 2020 14:39:34 +0100 [thread overview]
Message-ID: <CACT4Y+bp=jmo-WAZUCxT04G-DtbvZmf29KEToq1EMGB0gEpDOw@mail.gmail.com> (raw)
In-Reply-To: <00000000000043f47d0596c26e68@google.com>
On Thu, Nov 7, 2019 at 3:25 PM syzbot
<syzbot+2a89b1fb6539ff150c16@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this bug was fixed by commit:
>
> commit 32aaf0553df99cc4314f6e9f43216cd83afc6c20
> Author: Pengfei Li <lpf.vector@gmail.com>
> Date: Mon Sep 23 22:36:58 2019 +0000
>
> mm/compaction.c: remove unnecessary zone parameter in
> isolate_migratepages()
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=159dcaaae00000
> start commit: c6dd78fc Merge branch 'x86-urgent-for-linus' of git://git...
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=3c8985c08e1f9727
> dashboard link: https://syzkaller.appspot.com/bug?extid=2a89b1fb6539ff150c16
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1456f9d0600000
>
> If the result looks correct, please mark the bug fixed by replying with:
>
> #syz fix: mm/compaction.c: remove unnecessary zone parameter in
> isolate_migratepages()
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
This does not look like the right commit. The bug happened only twice
long time ago, so:
#syz invalid
prev parent reply other threads:[~2020-11-11 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 19:18 INFO: rcu detected stall in do_swap_page syzbot
2019-11-07 14:25 ` syzbot
2020-11-11 13:39 ` 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+bp=jmo-WAZUCxT04G-DtbvZmf29KEToq1EMGB0gEpDOw@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2a89b1fb6539ff150c16@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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).