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 6.1
Date: Wed, 23 Nov 2022 23:40:37 -0500 [thread overview]
Message-ID: <Y371xdJURvBvgGOi@mit.edu> (raw)
The following changes since commit f0c4d9fc9cc9462659728d168387191387e903cc:
Linux 6.1-rc4 (2022-11-06 15:07:11 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_stable2
for you to fetch changes up to 4e3c51f4e805291b057d12f5dda5aeb50a538dc4:
fs: do not update freeing inode i_io_list (2022-11-22 17:00:00 -0500)
----------------------------------------------------------------
Fix a regression in the lazytime code that was introduced in v6.1-rc1,
and a use-after-free that can be triggered by a maliciously corrupted
file system.
----------------------------------------------------------------
Baokun Li (1):
ext4: fix use-after-free in ext4_ext_shift_extents
Svyatoslav Feldsherov (1):
fs: do not update freeing inode i_io_list
fs/ext4/extents.c | 18 +++++++++++++-----
fs/fs-writeback.c | 30 +++++++++++++++++++-----------
2 files changed, 32 insertions(+), 16 deletions(-)
reply other threads:[~2022-11-24 4:40 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=Y371xdJURvBvgGOi@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).