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 v5.13
Date: Sun, 6 Jun 2021 10:21:03 -0400 [thread overview]
Message-ID: <YLzZz/Mh2HQQd80+@mit.edu> (raw)
The following changes since commit 6c0912739699d8e4b6a87086401bf3ad3c59502d:
ext4: wipe ext4_dir_entry2 upon file deletion (2021-04-22 16:51:23 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_stable
for you to fetch changes up to e71f99f2dfb45f4e7203a0732e85f71ef1d04dab:
ext4: Only advertise encrypted_casefold when encryption and unicode are enabled (2021-06-06 10:10:23 -0400)
----------------------------------------------------------------
Miscellaneous ext4 bug fixes for v5.13
----------------------------------------------------------------
Alexey Makhalov (1):
ext4: fix memory leak in ext4_fill_super
Daniel Rosenberg (2):
ext4: fix no-key deletion for encrypt+casefold
ext4: Only advertise encrypted_casefold when encryption and unicode are enabled
Harshad Shirwadkar (1):
ext4: fix fast commit alignment issues
Phillip Potter (1):
ext4: fix memory leak in ext4_mb_init_backend on error path.
Ritesh Harjani (1):
ext4: fix accessing uninit percpu counter variable with fast_commit
Ye Bin (1):
ext4: fix bug on in ext4_es_cache_extent as ext4_split_extent_at failed
fs/ext4/extents.c | 43 ++++++++-------
fs/ext4/fast_commit.c | 170 +++++++++++++++++++++++++++++++---------------------------
fs/ext4/fast_commit.h | 19 -------
fs/ext4/ialloc.c | 6 ++-
fs/ext4/mballoc.c | 2 +-
fs/ext4/namei.c | 6 ++-
fs/ext4/super.c | 11 +++-
fs/ext4/sysfs.c | 4 ++
8 files changed, 135 insertions(+), 126 deletions(-)
next reply other threads:[~2021-06-06 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 14:21 Theodore Ts'o [this message]
2021-06-06 22:48 ` [GIT PULL] ext4 fixes for v5.13 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=YLzZz/Mh2HQQd80+@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 read-only IMAP folder(s) and NNTP newsgroup(s).