Linux EXT4 FS development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Josef Bacik" <josef@toxicpanda.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH] ext2: only flush DIRSYNC directories on every change
Date: Tue, 27 Oct 2026 18:46:46 +0000	[thread overview]
Message-ID: <sashiko-outbox-187037@kernel.org> (raw)
In-Reply-To: <20261027-b4-ext2-dirsync-v1-1-3dcd012d518d@toxicpanda.com>

> Every change of an ext2 directory is written to disk before the system call
> returns, whether the directory is DIRSYNC or not: its pages with
> filemap_write_and_wait() and its inode with sync_inode_metadata().
> 
> Writes which reach the device for 2000 files, and 200 directories, in a
> directory without DIRSYNC, with the flusher turned off:
> 
>             create   rename   unlink   mkdir
>     before    4000     8000     4000     800
>     after        0        0        0       0
> 
> In a directory with chattr +D the numbers are those of "before", before and
> after.
> 
> commit bc943f4872a7 ("ext2: Don't flush page immediately for DIRSYNC
> directories") moved the flush from ext2_commit_chunk() to the new
> ext2_handle_dirsync().  The IS_DIRSYNC() check which was around it didn't
> move along.
> 
> Fix by putting the check into ext2_handle_dirsync().
> 
> Fixes: bc943f4872a7 ("ext2: Don't flush page immediately for DIRSYNC directories")
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261027-b4-ext2-dirsync-v1-1-3dcd012d518d@toxicpanda.com?part=1


      reply	other threads:[~2026-10-27 18:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 18:43 [PATCH] ext2: only flush DIRSYNC directories on every change Josef Bacik
2026-10-27 18:46 ` sashiko-bot [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=sashiko-outbox-187037@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tytso@mit.edu \
    /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