linux-ext4.vger.kernel.org archive mirror
 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 fixes for 6.4-rc5
Date: Wed, 31 May 2023 11:45:52 -0400	[thread overview]
Message-ID: <20230531154552.GA814122@mit.edu> (raw)

The following changes since commit 7877cb91f1081754a1487c144d85dc0d2e2e7fc4:

  Linux 6.4-rc4 (2023-05-28 07:49:00 -0400)

are available in the Git repository at:

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

for you to fetch changes up to eb1f822c76beeaa76ab8b6737ab9dc9f9798408c:

  ext4: enable the lazy init thread when remounting read/write (2023-05-30 15:33:57 -0400)

----------------------------------------------------------------
Fix two regressions in ext4 and a number of issues reported by syzbot.

----------------------------------------------------------------
Jan Kara (1):
      ext4: fix fsync for non-directories

Theodore Ts'o (5):
      ext4: add EA_INODE checking to ext4_iget()
      ext4: set lockdep subclass for the ea_inode in ext4_xattr_inode_cache_find()
      ext4: disallow ea_inodes with extended attributes
      ext4: add lockdep annotations for i_data_sem for ea_inode's
      ext4: enable the lazy init thread when remounting read/write

 fs/ext4/ext4.h  |  5 ++++-
 fs/ext4/fsync.c |  7 +++++++
 fs/ext4/inode.c | 34 +++++++++++++++++++++++++++++-----
 fs/ext4/super.c | 24 ++++++++++++------------
 fs/ext4/xattr.c | 41 ++++++++++++-----------------------------
 5 files changed, 64 insertions(+), 47 deletions(-)

                 reply	other threads:[~2023-05-31 15:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230531154552.GA814122@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;
as well as URLs for NNTP newsgroup(s).