From: Nikolay Amiantov <ab@fmap.me>
To: Miklos Szeredi <miklos@szeredi.hu>, Matthew Wilcox <willy@infradead.org>
Cc: fuse-devel@lists.sourceforge.net,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
fuse-devel@lists.linux.dev, linux-mm <linux-mm@kvack.org>
Subject: Re: [fuse-devel] Debugging a stale kernel cache during file growth
Date: Mon, 4 May 2026 23:49:22 +0700 [thread overview]
Message-ID: <9fe5ff50-4c1c-49ee-a8c2-4cacc3c6781d@fmap.me> (raw)
In-Reply-To: <CAJfpegtAeyMRENdneJkJrMKu8Uwnyk9LYBThjvTrFjHmPr6O_g@mail.gmail.com>
Kindly bringing this discussion up.
On 4/17/26 20:48, Miklos Szeredi wrote:
> Should that code check for a truncated page and retry?
If I understand you correctly, this can be accomplished with a new page
flag because there's no other way to find out the truncation happened;
would you say this is the right way forward?
Sadly I didn't have time to try and make a PoC fix yet, but I want to
try tackle it this weekend; meanwhile, any guidance is appreciated!
Thanks,
Nikolay.
next prev parent reply other threads:[~2026-05-04 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <898a4e10-6193-4671-b3b1-7c7bc562a671@fmap.me>
[not found] ` <CAOQ4uxjoS-PvnZ2poh0bx0C6ocTYwuEpfV0q5md15SjS620OMg@mail.gmail.com>
2026-04-16 12:12 ` [fuse-devel] Debugging a stale kernel cache during file growth Miklos Szeredi
2026-04-16 12:41 ` Nikolay Amiantov
2026-04-16 12:49 ` Nikolay Amiantov
2026-04-16 23:19 ` Matthew Wilcox
2026-04-17 6:24 ` Nikolay Amiantov
2026-04-17 13:48 ` Miklos Szeredi
2026-05-04 16:49 ` Nikolay Amiantov [this message]
2026-04-16 22:54 ` Matthew Wilcox
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=9fe5ff50-4c1c-49ee-a8c2-4cacc3c6781d@fmap.me \
--to=ab@fmap.me \
--cc=amir73il@gmail.com \
--cc=fuse-devel@lists.linux.dev \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miklos@szeredi.hu \
--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