From: Linus Torvalds <torvalds@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [GIT PULL] Rare page cache data corruption fix
Date: Fri, 22 Apr 2022 13:35:03 -0700 [thread overview]
Message-ID: <CAHk-=wjn-V-b=w=4GS_nJQ1nsVcJm0FPTv2Ene_xP_AWPBBFsg@mail.gmail.com> (raw)
In-Reply-To: <YmMF32RlCn2asAhc@casper.infradead.org>
On Fri, Apr 22, 2022 at 12:45 PM Matthew Wilcox <willy@infradead.org> wrote:
>
> Syzbot found a nasty race between large page splitting and page lookup.
> Details in the commit log, but fortunately it has a reliable reproducer.
The commit message does mention it ("I have not added a new test for
this bug."), but I'll echo it anyway, since you say it can be reliably
reproduced - getting that repro into the testsuite would be lovely.
Linus
next prev parent reply other threads:[~2022-04-22 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 19:45 Matthew Wilcox
2022-04-22 20:35 ` Linus Torvalds [this message]
2022-04-22 20:46 ` pr-tracker-bot
2022-04-30 19:22 ` Andrew Morton
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='CAHk-=wjn-V-b=w=4GS_nJQ1nsVcJm0FPTv2Ene_xP_AWPBBFsg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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