linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Brian Foster <bfoster@redhat.com>, linux-mm@kvack.org
Cc: Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH v3 0/3] tmpfs: zero post-eof ranges on file extension
Date: Tue, 25 Nov 2025 10:20:44 +0800	[thread overview]
Message-ID: <8f1c8ac4-208b-4a7d-8a57-721201c29f02@linux.alibaba.com> (raw)
In-Reply-To: <20251121152246.1023918-1-bfoster@redhat.com>



On 2025/11/21 23:22, Brian Foster wrote:
> Hi all,
> 
> Apologies for the quicker than expected respin here, but during
> discussion with Baolin on v2 it became apparent that I factored the
> first two patches in an unnecessarily confusing way, and I wanted to get
> that resolved more quickly. Otherwise there are a few smaller changes
> here that I think are incremental improvements.
> 
> Baolin, I left off the R-b tag from v2 just out of caution and how I
> reworked the first two patches. The end result is mostly similar, but
> I'd appreciate a quick look before adding that back. Otherwise most of
> the functionality here should be the same as v2.
> 
> Thoughts, reviews, flames appreciated.

Overall LGTM. And I tried to do some tmpfs read/write tests, and I 
didn't notice any obvious regressions. Anyway, let's wait and see if 
Hugh has any input. Thanks for your work.

> v3:
> - Reorder changes in patches 1-2 to factor out existing logic first.
> - Use local scope variable in shmem_writeout() fallocend block.
> - Tweak combined zeroing logic in shmem_writeout().
> - Clean up commit logs.
> v2: https://lore.kernel.org/linux-mm/20251112162522.412295-1-bfoster@redhat.com/
> - Rework to zero uptodate post-eof folios on writeout and full range
>    from EOF on size extension.
> - Misc. cleanups: variable renames (pos -> end), code relocation,
>    comment cleanups/removal.
> - Update commit log to call out POSIX requirement.
> v1: https://lore.kernel.org/linux-mm/20250625184930.269727-1-bfoster@redhat.com/
> 
> Brian Foster (3):
>    tmpfs: factor out folio zeroing logic at writeout time
>    tmpfs: zero post-eof folio ranges on swapout
>    tmpfs: zero post-eof ranges on file extension
> 
>   mm/shmem.c | 135 ++++++++++++++++++++++++++++++++++++++++++++---------
>   1 file changed, 114 insertions(+), 21 deletions(-)
> 



      parent reply	other threads:[~2025-11-25  2:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 15:22 Brian Foster
2025-11-21 15:22 ` [PATCH v3 1/3] tmpfs: factor out folio zeroing logic at writeout time Brian Foster
2025-11-21 15:22 ` [PATCH v3 2/3] tmpfs: zero post-eof folio ranges on swapout Brian Foster
2025-11-21 15:22 ` [PATCH v3 3/3] tmpfs: zero post-eof ranges on file extension Brian Foster
2025-11-25  2:20 ` Baolin Wang [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=8f1c8ac4-208b-4a7d-8a57-721201c29f02@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=bfoster@redhat.com \
    --cc=hughd@google.com \
    --cc=linux-mm@kvack.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