From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
Linux Kernel Developers List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ext4 changes for 6.19-rc1
Date: Tue, 2 Dec 2025 23:32:28 -0500 [thread overview]
Message-ID: <20251203043228.GA1712448@mit.edu> (raw)
The following changes since commit 6146a0f1dfae5d37442a9ddcba012add260bceb0:
Linux 6.18-rc4 (2025-11-02 11:28:02 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus-6.19-rc1
for you to fetch changes up to 91ef18b567dae84c0cea9b996d933c856e366f52:
ext4: mark inodes without acls in __ext4_iget() (2025-11-28 22:35:28 -0500)
----------------------------------------------------------------
New features and improvements for the ext4 file system
* Optimize online defragmentation by using folios instead of individual
buffer heads
* Improve error codes stored in the superblock when the journal aborts
* Minor cleanups and clarifications in ext4_map_blocks()
* Add documentation of the casefold and encrypt flags
* Add support for file systems with a blocksize greater than the pagesize
* Improve performance by enabling the caching the fact that an inode does
not have a Posix ACL.
Various Bug Fixes
* Fix false positive compliants from smatch
* Fix error code which is returned by ext4fs_dirhash() when Siphash is
used without the encryption key
* Fix races when writing to inline data files which could trigger a BUG
* Fix potential NULL dereference when there is an corrupt file system with
an extended attribute value stored in a inode
* Fix false positive lockdep report when syzbot uses ext4 and ocfs2 together
* Fix false positive reported by DEPT by adjusting lock annotation
* Avoid a potential BUG_ON in jbd2 when a file system is massively corrupted
* Fix a WARN_ON when superblock is corrupted with a non-NULL terminated
mount options field
* Add check if the userspace passes in a non-NULL terminated mount options
field to EXT4_IOC_SET_TUNE_SB_PARAM
* Fix a potential journal checksum failure whena file system is copied while
it is mounted read-only
* Fix a potential potential orphan file tracking error which only showed
on 32-bit systems
* Fix assertion checks in mballoc (which have to be explicitly enbled by
manually enabling AGGRESSIVE_CHECKS and recompiling)
* Avoid complaining about overly large orphan files created by mke2fs with
with file systems with a 64k block size
----------------------------------------------------------------
Alexey Nepomnyashih (1):
ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock()
Baokun Li (22):
ext4: align max orphan file size with e2fsprogs limit
ext4: remove page offset calculation in ext4_block_truncate_page()
ext4: remove PAGE_SIZE checks for rec_len conversion
ext4: make ext4_punch_hole() support large block size
ext4: enable DIOREAD_NOLOCK by default for BS > PS as well
ext4: introduce s_min_folio_order for future BS > PS support
ext4: support large block size in ext4_calculate_overhead()
ext4: support large block size in ext4_readdir()
ext4: add EXT4_LBLK_TO_B macro for logical block to bytes conversion
ext4: add EXT4_LBLK_TO_PG and EXT4_PG_TO_LBLK for block/page conversion
ext4: support large block size in ext4_mb_load_buddy_gfp()
ext4: support large block size in ext4_mb_get_buddy_page_lock()
ext4: support large block size in ext4_mb_init_cache()
ext4: prepare buddy cache inode for BS > PS with large folios
ext4: support large block size in ext4_mpage_readpages()
ext4: support large block size in ext4_block_write_begin()
ext4: support large block size in mpage_map_and_submit_buffers()
ext4: support large block size in mpage_prepare_extent_to_map()
ext4: make data=journal support large block size
ext4: support verifying data from large folios with fs-verity
ext4: add checks for large folio incompatibilities when BS > PS
ext4: enable block size larger than page size
Byungchul Park (1):
jbd2: use a weaker annotation in journal handling
Daniel Tang (1):
Documentation: ext4: Document casefold and encrypt flags
Deepanshu Kartikey (1):
ext4: refresh inline data size before write operations
Fedor Pchelkin (2):
ext4: fix string copying in parse_apply_sb_mount_options()
ext4: check if mount_opts is NUL-terminated in ext4_ioctl_set_tune_sb()
Haibo Chen (1):
ext4: clear i_state_flags when alloc inode
Haodong Tian (1):
fs/ext4: fix typo in comment
Jan Kara (1):
ext4: mark inodes without acls in __ext4_iget()
Julian Sun (1):
ext4: make error code in __ext4fs_dirhash() consistent.
Karina Yankevich (1):
ext4: xattr: fix null pointer deref in ext4_raw_inode()
Ranganath V N (1):
fs: ext4: fix uninitialized symbols
Tetsuo Handa (1):
jbd2: use a per-journal lock_class_key for jbd2_trans_commit_key
Wengang Wang (1):
jbd2: store more accurate errno in superblock when possible
Yang Erkun (3):
ext4: rename EXT4_GET_BLOCKS_PRE_IO
ext4: cleanup for ext4_map_blocks
ext4: correct the comments place for EXT4_EXT_MAY_ZEROOUT
Ye Bin (2):
jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted
jbd2: fix the inconsistency between checksum and data in memory for journal sb
Yongjian Sun (2):
ext4: fix incorrect group number assertion in mb_check_buddy
ext4: improve integrity checking in __mb_check_buddy by enhancing order-0 validation
Zhang Yi (12):
ext4: correct the checking of quota files before moving extents
ext4: introduce seq counter for the extent status entry
ext4: make ext4_es_lookup_extent() pass out the extent seq counter
ext4: pass out extent seq counter when mapping blocks
ext4: use EXT4_B_TO_LBLK() in mext_check_arguments()
ext4: add mext_check_validity() to do basic check
ext4: refactor mext_check_arguments()
ext4: rename mext_page_mkuptodate() to mext_folio_mkuptodate()
ext4: introduce mext_move_extent()
ext4: switch to using the new extent movement method
ext4: add large folios support for moving extents
ext4: add two trace points for moving extents
Zhihao Cheng (3):
ext4: remove page offset calculation in ext4_block_zero_page_range()
ext4: rename 'page' references to 'folio' in multi-block allocator
ext4: support large block size in __ext4_block_zero_page_range()
Documentation/filesystems/ext4/inodes.rst | 2 +
Documentation/filesystems/ext4/super.rst | 4 +-
fs/ext4/balloc.c | 2 +-
fs/ext4/dir.c | 8 +-
fs/ext4/ext4.h | 50 +--
fs/ext4/ext4_jbd2.c | 3 +-
fs/ext4/extents.c | 28 +-
fs/ext4/extents_status.c | 31 +-
fs/ext4/extents_status.h | 2 +-
fs/ext4/hash.c | 2 +-
fs/ext4/ialloc.c | 1 -
fs/ext4/inline.c | 14 +-
fs/ext4/inode.c | 165 +++++-----
fs/ext4/ioctl.c | 14 +-
fs/ext4/mballoc.c | 188 ++++++-----
fs/ext4/move_extent.c | 786 +++++++++++++++++++++-----------------------
fs/ext4/namei.c | 18 +-
fs/ext4/orphan.c | 4 +-
fs/ext4/readpage.c | 7 +-
fs/ext4/super.c | 72 +++-
fs/ext4/sysfs.c | 6 +
fs/ext4/verity.c | 2 +-
fs/ext4/xattr.c | 6 +-
fs/jbd2/checkpoint.c | 2 +-
fs/jbd2/journal.c | 35 +-
fs/jbd2/transaction.c | 26 +-
include/linux/jbd2.h | 6 +
include/trace/events/ext4.h | 99 +++++-
28 files changed, 872 insertions(+), 711 deletions(-)
next reply other threads:[~2025-12-03 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 4:32 Theodore Ts'o [this message]
2025-12-04 4:48 ` [GIT PULL] ext4 changes for 6.19-rc1 pr-tracker-bot
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=20251203043228.GA1712448@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.