From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Developers List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ext4 bug fixes for v6.6-rc2
Date: Sun, 17 Sep 2023 01:02:35 -0400 [thread overview]
Message-ID: <20230917050235.GA1702062@mit.edu> (raw)
The following changes since commit 768d612f79822d30a1e7d132a4d4b05337ce42ec:
ext4: fix slab-use-after-free in ext4_es_insert_extent() (2023-08-27 11:27:13 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus-6.6-rc2
for you to fetch changes up to 7fda67e8c3ab6069f75888f67958a6d30454a9f6:
ext4: fix rec_len verify error (2023-09-14 12:07:07 -0400)
----------------------------------------------------------------
Regression and bug fixes for ext4.
----------------------------------------------------------------
Jan Kara (2):
ext4: move setting of trimmed bit into ext4_try_to_trim_range()
ext4: do not let fstrim block system suspend
Li Zetao (1):
jbd2: Fix memory leak in journal_init_common()
Matthew Wilcox (Oracle) (1):
buffer: Make bh_offset() work for compound pages
Ritesh Harjani (IBM) (1):
jbd2: Remove page size assumptions
Shida Zhang (1):
ext4: fix rec_len verify error
fs/ext4/mballoc.c | 54 ++++++++++++++++++++++++++++++++--------------------
fs/ext4/namei.c | 26 ++++++++++++++-----------
fs/jbd2/commit.c | 16 ++++++----------
fs/jbd2/journal.c | 2 ++
fs/jbd2/transaction.c | 12 ++++--------
include/linux/buffer_head.h | 5 ++++-
6 files changed, 64 insertions(+), 51 deletions(-)
next reply other threads:[~2023-09-17 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 5:02 Theodore Ts'o [this message]
2023-09-17 18:24 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-09-17 5:01 Theodore Ts'o
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=20230917050235.GA1702062@mit.edu \
--to=tytso@mit.edu \
--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
all inboxes | Powered by JetHome®