From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+9301f2f33873407d5b33@syzkaller.appspotmail.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: WARNING in wp_page_copy
Date: Wed, 11 Nov 2020 14:34:36 +0100 [thread overview]
Message-ID: <CACT4Y+aH=eGwrJba6bbRPeZ5CfEwu0Ex2b6V2VkuM-58h8F9bw@mail.gmail.com> (raw)
In-Reply-To: <0000000000004162e805a190c456@google.com>
On Tue, Mar 24, 2020 at 3:47 AM syzbot
<syzbot+9301f2f33873407d5b33@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this bug was fixed by commit:
>
> commit c3e5ea6ee574ae5e845a40ac8198de1fb63bb3ab
> Author: Kirill A. Shutemov <kirill@shutemov.name>
> Date: Fri Mar 6 06:28:32 2020 +0000
>
> mm: avoid data corruption on CoW fault into PFN-mapped VMA
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1170c813e00000
> start commit: e31736d9 Merge tag 'nios2-v5.5-rc2' of git://git.kernel.or..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=79f79de2a27d3e3d
> dashboard link: https://syzkaller.appspot.com/bug?extid=9301f2f33873407d5b33
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10fd9fb1e00000
>
> If the result looks correct, please mark the bug fixed by replying with:
>
> #syz fix: mm: avoid data corruption on CoW fault into PFN-mapped VMA
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
#syz fix: mm: avoid data corruption on CoW fault into PFN-mapped VMA
prev parent reply other threads:[~2020-11-11 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000a6f2030598bbe38c@google.com>
[not found] ` <0000000000000e32950599ac5a96@google.com>
[not found] ` <20191216150017.GA27202@linux.fritz.box>
[not found] ` <CAJ8uoz3nCxcmnPonNunYhswskidn=PnN8=4_jXW4B=Xu4k_DoQ@mail.gmail.com>
2019-12-17 13:27 ` WARNING in wp_page_copy Magnus Karlsson
2019-12-17 15:40 ` Catalin Marinas
2019-12-17 15:57 ` Magnus Karlsson
2019-12-17 22:38 ` Catalin Marinas
2019-12-18 15:00 ` Magnus Karlsson
2019-12-18 15:11 ` Kirill A. Shutemov
2019-12-17 20:16 ` syzbot
2020-03-24 2:47 ` syzbot
2020-11-11 13:34 ` 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+aH=eGwrJba6bbRPeZ5CfEwu0Ex2b6V2VkuM-58h8F9bw@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+9301f2f33873407d5b33@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).