From: Matthew Wilcox <willy@infradead.org>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mm: Remove bogus VM_BUG_ON
Date: Wed, 18 Aug 2021 17:45:25 +0100 [thread overview]
Message-ID: <YR05JVZwfAlZO9Wh@casper.infradead.org> (raw)
In-Reply-To: <2197941-297c-f820-aa57-fb5167794fb1@google.com>
On Wed, Aug 18, 2021 at 09:34:51AM -0700, Hugh Dickins wrote:
> On Wed, 18 Aug 2021, Matthew Wilcox (Oracle) wrote:
>
> > It is not safe to check page->index without holding the page lock.
> > It can be changed if the page is moved between the swap cache and the
> > page cache for a shmem file, for example. There is a VM_BUG_ON below
> > which checks page->index is correct after taking the page lock.
> >
> > Cc: stable@vger.kernel.org
> > Fixes: 5c211ba29deb ("mm: add and use find_lock_entries")
>
> I don't mind that VM_BUG_ON_PAGE() being removed, but question whether
> this Fixes anything, and needs to go to stable. Or maybe it's just that
> the shmem example is wrong - moving shmem from page to swap cache does
> not change page->index. Or maybe you have later changes in your tree
> which change that and do require this. Otherwise, I'll have to worry
> why my testing has missed it for six months.
I'm sorry, I think you're going to have to worry :-( Syzbot found
it initially:
https://lore.kernel.org/linux-mm/0000000000009cfcda05c926b34b@google.com/
and then I hit it today during my testing (which is definitely due to
further changes in my tree).
I should have added:
Reported-by: syzbot+c87be4f669d920c76330@syzkaller.appspotmail.com
next prev parent reply other threads:[~2021-08-18 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 14:49 [PATCH] mm: Remove bogus VM_BUG_ON Matthew Wilcox (Oracle)
2021-08-18 16:34 ` Hugh Dickins
2021-08-18 16:45 ` Matthew Wilcox [this message]
2021-08-19 20:42 ` Hugh Dickins
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=YR05JVZwfAlZO9Wh@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).