public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>, Jan Kara <jack@suse.cz>,
	John Garry <john.g.garry@oracle.com>,
	djwong@kernel.org, Ojaswin Mujoo <ojaswin@linux.ibm.com>,
	linux-fsdevel@vger.kernel.org,
	"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Subject: [PATCH v1 0/5] ext4: Minor fixes and improvements for atomic write series
Date: Mon, 19 May 2025 23:49:25 +0530	[thread overview]
Message-ID: <cover.1747677758.git.ritesh.list@gmail.com> (raw)

Some minor fixes and improvements on top of ext4's dev branch [1] for atomic
write patch series.

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/log/?h=dev

Patch-1: Is the fix needed after rebase on top of extent status cleanup.
Patch-2: warning fix for cocci
Patch-{3..5}: Minor improvements / simplifications.

Ritesh Harjani (IBM) (5):
  ext4: Unwritten to written conversion requires EXT4_EX_NOCACHE
  ext4: Simplify last in leaf check in ext4_map_query_blocks
  ext4: Rename and document EXT4_EX_FILTER to EXT4_EX_QUERY_FILTER
  ext4: Simplify flags in ext4_map_query_blocks()
  ext4: Add a WARN_ON_ONCE for querying LAST_IN_LEAF instead

 fs/ext4/ext4.h    | 8 +++++++-
 fs/ext4/extents.c | 6 ++++--
 fs/ext4/inode.c   | 9 +++------
 3 files changed, 14 insertions(+), 9 deletions(-)

--
2.49.0


             reply	other threads:[~2025-05-19 18:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19 18:19 Ritesh Harjani (IBM) [this message]
2025-05-19 18:19 ` [PATCH v1 1/5] ext4: Unwritten to written conversion requires EXT4_EX_NOCACHE Ritesh Harjani (IBM)
2025-05-20 14:36   ` Ojaswin Mujoo
2025-05-19 18:19 ` [PATCH v1 2/5] ext4: Simplify last in leaf check in ext4_map_query_blocks Ritesh Harjani (IBM)
2025-05-20 14:36   ` Ojaswin Mujoo
2025-05-19 18:19 ` [PATCH v1 3/5] ext4: Rename and document EXT4_EX_FILTER to EXT4_EX_QUERY_FILTER Ritesh Harjani (IBM)
2025-05-19 18:19 ` [PATCH v1 4/5] ext4: Simplify flags in ext4_map_query_blocks() Ritesh Harjani (IBM)
2025-05-19 18:19 ` [PATCH v1 5/5] ext4: Add a WARN_ON_ONCE for querying LAST_IN_LEAF instead Ritesh Harjani (IBM)
2025-05-20 14:37   ` Ojaswin Mujoo
2025-05-21 12:20 ` [PATCH v1 0/5] ext4: Minor fixes and improvements for atomic write series Theodore Ts'o

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=cover.1747677758.git.ritesh.list@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=djwong@kernel.org \
    --cc=jack@suse.cz \
    --cc=john.g.garry@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --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