public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
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 bug fixes for v6.15-rc2
Date: Sun, 13 Apr 2025 08:37:37 -0400	[thread overview]
Message-ID: <20250413123737.GA1116899@mit.edu> (raw)

The following changes since commit d5e206778e96e8667d3bde695ad372c296dc9353:

  ext4: fix OOB read when checking dotdot dir (2025-03-21 01:33:11 -0400)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus-6.15-rc2

for you to fetch changes up to 94824ac9a8aaf2fb3c54b4bdde842db80ffa555d:

  ext4: fix off-by-one error in do_split (2025-04-12 22:07:36 -0400)

----------------------------------------------------------------
A few more miscellaneous ext4 bug fixes and cleanups including some
syzbot failures and fixing a stale file handing refeencing an inode
previously used as a regular file, but which has been deleted and
reused as an ea_inode would result in ext4 erroneously consider this a
case of fs corrupotion.

----------------------------------------------------------------
Artem Sadovnikov (1):
      ext4: fix off-by-one error in do_split

Gustavo A. R. Silva (1):
      ext4: avoid -Wflex-array-member-not-at-end warning

Jann Horn (1):
      ext4: don't treat fhandle lookup of ea_inode as FS corruption

Ojaswin Mujoo (1):
      ext4: make block validity check resistent to sb bh corruption

Tom Vierjahn (1):
      Documentation: ext4: Add fields to ext4_super_block documentation

 Documentation/filesystems/ext4/super.rst | 20 ++++++++++++-----
 fs/ext4/block_validity.c                 |  5 ++---
 fs/ext4/inode.c                          | 75 +++++++++++++++++++++++++++++++++++++++++++-------------------
 fs/ext4/mballoc.c                        | 18 +++++++--------
 fs/ext4/namei.c                          |  2 +-
 5 files changed, 77 insertions(+), 43 deletions(-)

             reply	other threads:[~2025-04-13 12:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-13 12:37 Theodore Ts'o [this message]
2025-04-13 15:16 ` [GIT PULL] ext4 bug fixes for v6.15-rc2 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=20250413123737.GA1116899@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox