From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] ext4 changes for v5.12
Date: Thu, 25 Feb 2021 11:00:13 -0500 [thread overview]
Message-ID: <YDfJjd0JEhAHoC2n@mit.edu> (raw)
The following changes since commit 1048ba83fb1c00cd24172e23e8263972f6b5d9ac:
Linux 5.11-rc6 (2021-01-31 13:50:09 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus
for you to fetch changes up to 0a76945fd1ba2ab44da7b578b311efdfedf92e6c:
ext4: add .kunitconfig fragment to enable ext4-specific tests (2021-02-11 23:16:30 -0500)
----------------------------------------------------------------
Miscellaneous ext4 cleanups and bug fixes. Pretty boring this
cycle...
----------------------------------------------------------------
Daejun Park (1):
ext4: Change list_for_each* to list_for_each_entry*
Daniel Latypov (1):
ext4: add .kunitconfig fragment to enable ext4-specific tests
Eric Whitney (1):
ext4: reset retry counter when ext4_alloc_file_blocks() makes progress
Geert Uytterhoeven (1):
ext: EXT4_KUNIT_TESTS should depend on EXT4_FS instead of selecting it
Theodore Ts'o (2):
ext4: don't try to processed freed blocks until mballoc is initialized
ext4: fix potential htree index checksum corruption
Vinicius Tinti (1):
ext4: factor out htree rep invariant check
Zheng Yongjun (1):
ext4: use DEFINE_MUTEX() for mutex lock
fs/ext4/.kunitconfig | 3 +++
fs/ext4/Kconfig | 3 +--
fs/ext4/extents.c | 16 ++++++++--------
fs/ext4/fast_commit.c | 29 +++++++++++------------------
fs/ext4/namei.c | 45 +++++++++++++++++++++++++++------------------
fs/ext4/super.c | 12 +++++++++---
6 files changed, 59 insertions(+), 49 deletions(-)
create mode 100644 fs/ext4/.kunitconfig
next reply other threads:[~2021-02-25 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 16:00 Theodore Ts'o [this message]
2021-02-25 18:36 ` [GIT PULL] ext4 changes for v5.12 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=YDfJjd0JEhAHoC2n@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).