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 bug fixes for 6.1
Date: Sun, 6 Nov 2022 01:18:11 -0500 [thread overview]
Message-ID: <Y2dRoyP5tKIZj/b4@mit.edu> (raw)
The following changes since commit 4c86114194e644b6da9107d75910635c9e87179e:
Merge tag 'iomap-6.1-merge-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux (2022-10-06 17:57:50 -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 0d043351e5baf3857f915367deba2a518b6a0809:
ext4: fix fortify warning in fs/ext4/fast_commit.c:1551 (2022-11-06 01:07:59 -0400)
----------------------------------------------------------------
Fix a number of bug fixes, including some regressions, the most
serious of which was one which would cause online resizes to fail with
file systems with metadata checksums enabled. Also fix a warning
caused by the newly added fortify string checker, plus some bugs that
were found using fuzzed file systems.
----------------------------------------------------------------
Jason Yan (1):
ext4: fix wrong return err in ext4_load_and_init_journal()
Luís Henriques (1):
ext4: fix BUG_ON() when directory entry has invalid rec_len
Theodore Ts'o (2):
ext4: update the backup superblock's at the end of the online resize
ext4: fix fortify warning in fs/ext4/fast_commit.c:1551
Ye Bin (1):
ext4: fix warning in 'ext4_da_release_space'
fs/ext4/fast_commit.c | 5 +++--
fs/ext4/ioctl.c | 3 +--
fs/ext4/migrate.c | 3 ++-
fs/ext4/namei.c | 10 +++++++++-
fs/ext4/resize.c | 5 +++++
fs/ext4/super.c | 2 +-
6 files changed, 21 insertions(+), 7 deletions(-)
next reply other threads:[~2022-11-06 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 6:18 Theodore Ts'o [this message]
2022-11-06 18:49 ` [GIT PULL] ext4 bug fixes for 6.1 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=Y2dRoyP5tKIZj/b4@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