From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: [GIT PULL] ext4 fixes for v6.4-rc2
Date: Sat, 13 May 2023 20:28:41 -0400 [thread overview]
Message-ID: <ZGArOUgijBkG1y3G@mit.edu> (raw)
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
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 2a534e1d0d1591e951f9ece2fb460b2ff92edabd:
ext4: bail out of ext4_xattr_ibody_get() fails for any reason (2023-05-13 18:05:05 -0400)
----------------------------------------------------------------
Some ext4 bug fixes (mostly to address Syzbot reports) for v6.4-rc2.
----------------------------------------------------------------
Baokun Li (1):
ext4: check iomap type only if ext4_iomap_begin() does not fail
Jan Kara (3):
ext4: fix lockdep warning when enabling MMP
ext4: avoid deadlock in fs reclaim with page writeback
ext4: fix data races when using cached status extents
Theodore Ts'o (10):
ext4: allow ext4_get_group_info() to fail
ext4: remove a BUG_ON in ext4_mb_release_group_pa()
ext4: fix invalid free tracking in ext4_xattr_move_to_block()
ext4: don't clear SB_RDONLY when remounting r/w until quota is re-enabled
ext4: improve error handling from ext4_dirhash()
ext4: improve error recovery code paths in __ext4_remount()
ext4: fix deadlock when converting an inline directory in nojournal mode
ext4: add indication of ro vs r/w mounts in the mount message
ext4: add bounds checking in get_max_inline_xattr_value_size()
ext4: bail out of ext4_xattr_ibody_get() fails for any reason
Tudor Ambarus (1):
ext4: avoid a potential slab-out-of-bounds in ext4_group_desc_csum
Ye Bin (1):
ext4: fix WARNING in mb_find_extent
fs/ext4/balloc.c | 43 ++++++++++++++++++++++++++++++++++++++++-
fs/ext4/ext4.h | 39 ++++++++++++++++++++++++-------------
fs/ext4/extents_status.c | 30 +++++++++++++----------------
fs/ext4/hash.c | 6 +++++-
fs/ext4/ialloc.c | 12 ++++++++----
fs/ext4/inline.c | 17 ++++++++++++++---
fs/ext4/inode.c | 20 ++++++++++---------
fs/ext4/mballoc.c | 70 +++++++++++++++++++++++++++++++++++++++++++++++++++++++------------
fs/ext4/migrate.c | 11 ++++++-----
fs/ext4/mmp.c | 30 ++++++++++++++++++++---------
fs/ext4/namei.c | 53 ++++++++++++++++++++++++++++++++++----------------
fs/ext4/super.c | 37 +++++++++++++++++++++++------------
fs/ext4/xattr.c | 5 +++--
13 files changed, 269 insertions(+), 104 deletions(-)
next reply other threads:[~2023-05-14 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 0:28 Theodore Ts'o [this message]
2023-05-14 0:52 ` [GIT PULL] ext4 fixes for v6.4-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=ZGArOUgijBkG1y3G@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