From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Ayush Ranjan <ayushr@modal.com>, Pedro Falcato <pfalcato@suse.de>
Cc: Hugh Dickins <hughd@google.com>,
Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>, David Hildenbrand <david@kernel.org>,
Gregory Price <gourry@gourry.net>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] shmem: FALLOC_FL_PUNCH_HOLE vs fault-around race corrupts page cache / rss counters
Date: Thu, 8 Oct 2026 15:58:56 +0800 [thread overview]
Message-ID: <6aa5a165-3ba6-4974-b549-fed7318ead49@linux.alibaba.com> (raw)
In-Reply-To: <20261003033107.1488699-1-ayushr@modal.com>
On 10/3/26 11:31 AM, Ayush Ranjan wrote:
> Hi all,
>
> Gentle ping on this.
Sorry for the late reply due to my vacation.
The reproducer in my previous mail [1] triggers
> "Bad page cache ... still mapped when deleted" on 6.18.46 within a
> couple of minutes on a 128-CPU bare-metal box, with no fork() and no
> gVisor involved.
>
> We continue to hit this in production at low frequency, so I am happy
> to test patches or collect more data if that would help.
Now I can reproduce this issue on my machine with the latest mm-unstable
branch, and I understand the race. I have confirmed that Andrew's patch
can fix it. You can try Andrew's patch.
next prev parent reply other threads:[~2026-10-08 7:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 6:16 Ayush Ranjan
2026-09-24 7:12 ` David Hildenbrand (Arm)
2026-09-24 8:34 ` Pedro Falcato
2026-09-24 9:15 ` Jan Kara
2026-09-25 5:32 ` Ayush Ranjan
2026-09-24 9:30 ` Baolin Wang
2026-09-25 5:33 ` Ayush Ranjan
2026-09-25 5:30 ` Ayush Ranjan
2026-09-25 6:50 ` Ayush Ranjan
2026-10-03 3:31 ` Ayush Ranjan
2026-10-05 5:28 ` Andrew Morton
2026-10-08 9:24 ` Jan Kara
2026-10-08 15:23 ` Andrew Morton
2026-10-08 15:31 ` Andrew Morton
2026-10-09 6:46 ` Baolin Wang
2026-10-08 13:07 ` Gregory Price
2026-10-08 7:58 ` Baolin Wang [this message]
2026-10-08 9:26 ` Jan Kara
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=6aa5a165-3ba6-4974-b549-fed7318ead49@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=ayushr@modal.com \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pfalcato@suse.de \
--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
all inboxes | Powered by JetHome®