Linux EXT4 FS development
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>
Subject: [PATCH 0/2 -v3] ext4: scoped NOFS for the handle in nojournal mode
Date: Tue, 21 Jul 2026 10:01:34 -0400	[thread overview]
Message-ID: <20260721140152.461286-1-tytso@mit.edu> (raw)

This patch series makes it safe to remove the GFP_NOFS flag when an
active is handle and slightly optimized the data layout of the jbd2
handle.

Theodore Ts'o (2):
  ext4: enable scoped NOFS when starting a handle in nojournal mode
  jbd2: align h_type and h_line_no in the handle structure on byte
    boundaries

 fs/ext4/ext4_jbd2.c  | 36 ++++++++++++++++++++++--------------
 fs/ext4/ext4_jbd2.h  |  6 +-----
 fs/jbd2/journal.c    |  1 +
 include/linux/jbd2.h | 11 ++++++-----
 4 files changed, 30 insertions(+), 24 deletions(-)

Changes in v3:
  * Export ext4_handle_cache to fix a build break when ext4 is
    compiled as module
  * Add an optimization in how h_type and h_line_no is laid out
    in the jbd2_journal_handle structure.
Link to v2: https://lore.kernel.org/r/20260716144831.41290-1-tytso@mit.edu

Changes in v2:
  * Remove an unused variable in ext4_get_nojournal()
  * Add a safety check in case ext4_handle_valid() is passed a NULL
    pointer, even though the fucntion is documented that the caller
    must not be called with a NULL handle.
Link to v1: https://lore.kernel.org/r/20260625172223.88878-1-tytso@mit.edu

-- 
2.53.0


             reply	other threads:[~2026-07-21 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 14:01 Theodore Ts'o [this message]
2026-07-21 14:01 ` [PATCH 1/2] ext4: enable scoped NOFS when starting a handle in nojournal mode Theodore Ts'o
2026-07-22 22:55   ` Andreas Dilger
2026-07-21 14:01 ` [PATCH 2/2] jbd2: align h_type and h_line_no in the handle structure on byte boundaries 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=20260721140152.461286-1-tytso@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.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