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: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] ext4 changes for 6.3, part I
Date: Mon, 27 Feb 2023 23:25:27 -0500	[thread overview]
Message-ID: <Y/2CN+FpmGsfzgdE@mit.edu> (raw)

The following changes since commit 2241ab53cbb5cdb08a6b2d4688feb13971058f65:

  Linux 6.2-rc5 (2023-01-21 16:27:01 -0800)

are available in the Git repository at:

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

for you to fetch changes up to e3645d72f8865ffe36f9dc811540d40aa3c848d3:

  ext4: fix incorrect options show of original mount_opt and extend mount_opt2 (2023-02-25 15:39:08 -0500)

----------------------------------------------------------------
Improve performance for ext4 by allowing multiple process to perform
direct I/O writes to preallocated blocks by using a shared inode lock
instead of taking an exclusive lock.

In addition, multiple bug fixes and cleanups.

----------------------------------------------------------------
Baokun Li (3):
      ext4: fail ext4_iget if special inode unallocated
      ext4: update s_journal_inum if it changes after journal replay
      ext4: fix task hung in ext4_xattr_delete_inode

Eric Biggers (1):
      ext4: use ext4_fc_tl_mem in fast-commit replay path

Jan Kara (1):
      ext4: Fix possible corruption when moving a directory

Jun Nie (2):
      ext4: optimize ea_inode block expansion
      ext4: refuse to create ea block when umounted

Kees Cook (1):
      ext4: fix function prototype mismatch for ext4_feat_ktype

Tanmay Bhushan (1):
      ext4: remove dead code in updating backup sb

Theodore Ts'o (1):
      ext4: improve xattr consistency checking and error reporting

Wang Jianjian (1):
      ext4: don't show commit interval if it is zero

XU pengfei (1):
      ext4: remove unnecessary variable initialization

Ye Bin (1):
      ext4: init error handle resource before init group descriptors

Zhang Yi (2):
      ext4: dio take shared inode lock when overwriting preallocated blocks
      ext4: fix incorrect options show of original mount_opt and extend mount_opt2

Zhihao Cheng (1):
      jbd2: fix data missing when reusing bh which is ready to be checkpointed

zhanchengbin (1):
      ext4: fix inode tree inconsistency caused by ENOMEM

 fs/ext4/ext4.h        |   1 +
 fs/ext4/extents.c     |   2 +-
 fs/ext4/fast_commit.c |  44 +++++++++++++++-----------
 fs/ext4/file.c        |  34 +++++++++++++-------
 fs/ext4/inode.c       |  20 ++++++------
 fs/ext4/ioctl.c       |   3 --
 fs/ext4/namei.c       |  11 ++++++-
 fs/ext4/super.c       |  56 +++++++++++++++++++-------------
 fs/ext4/sysfs.c       |   7 +++-
 fs/ext4/xattr.c       | 172 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------------------------
 fs/jbd2/transaction.c |  50 +++++++++++++++++------------
 11 files changed, 253 insertions(+), 147 deletions(-)

             reply	other threads:[~2023-02-28  4:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28  4:25 Theodore Ts'o [this message]
2023-02-28 17:17 ` [GIT PULL] ext4 changes for 6.3, part I 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=Y/2CN+FpmGsfzgdE@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