All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: [GIT PULL] ext4 fixes for 6.19-rc6
Date: Sun, 18 Jan 2026 11:51:59 -0500	[thread overview]
Message-ID: <20260118165159.GA580401@mit.edu> (raw)

The following changes since commit 9ace4753a5202b02191d54e9fdf7f9e3d02b85eb:

  Linux 6.19-rc4 (2026-01-04 14:41:55 -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-rc6

for you to fetch changes up to d250bdf531d9cd4096fedbb9f172bb2ca660c868:

  ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (2026-01-18 11:23:10 -0500)

----------------------------------------------------------------
Ext4 bug fixes for 6.19:

   * Fix an inconsistency in structure size on 32-bit platforms caused by padding
     differences for the new EXT4_IOC_[GS]ET_TUNE_SB_PARAM ioctls
   * Fix a buffer leak on the error path when dropping the refcount an xattr
     value stored in an inode
   * Fix missing locking on the error path for the file defragmentation ioctl
     leading to a BUG

----------------------------------------------------------------
Arnd Bergmann (1):
      ext4: fix ext4_tune_sb_params padding

Julian Sun (1):
      ext4: add missing down_write_data_sem in mext_move_extent().

Yang Erkun (1):
      ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref

 fs/ext4/move_extent.c     | 2 ++
 fs/ext4/xattr.c           | 1 +
 include/uapi/linux/ext4.h | 2 +-
 3 files changed, 4 insertions(+), 1 deletion(-)

             reply	other threads:[~2026-01-18 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-18 16:51 Theodore Ts'o [this message]
2026-01-19 13:54 ` [GIT PULL] ext4 fixes for 6.19-rc6 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=20260118165159.GA580401@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@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.