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 fixes for 5.19-rc3
Date: Sat, 18 Jun 2022 20:30:49 -0400 [thread overview]
Message-ID: <Yq5uOVSUci3fv+Mw@mit.edu> (raw)
The following changes since commit b13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3:
Linux 5.19-rc2 (2022-06-12 16:11:37 -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 1f3ddff3755915a2b38de92d53508594de432d3d:
ext4: fix a doubled word "need" in a comment (2022-06-18 19:36:20 -0400)
----------------------------------------------------------------
Fix a variety of bugs, many of which were found by folks using fuzzing
or error injection. Also fix up how test_dummy_encryption mount
option is handled for the new mount API. Finally, fix/cleanup a
number of comments and ext4 Documentation files.
----------------------------------------------------------------
Baokun Li (2):
ext4: fix bug_on ext4_mb_use_inode_pa
ext4: correct the judgment of BUG in ext4_mb_normalize_request
Ding Xiang (1):
ext4: make variable "count" signed
Eric Biggers (1):
ext4: fix up test_dummy_encryption handling for new mount API
Jan Kara (1):
ext4: improve write performance with disabled delalloc
Shuqi Zhang (1):
ext4: use kmemdup() to replace kmalloc + memcpy
Wang Jianjian (2):
ext4: fix incorrect comment in ext4_bio_write_page()
ext4, doc: remove unnecessary escaping
Xiang wangx (1):
ext4: fix a doubled word "need" in a comment
Yang Li (1):
fs: fix jbd2_journal_try_to_free_buffers() kernel-doc comment
Ye Bin (1):
ext4: fix super block checksum incorrect after mount
Zhang Yi (2):
ext4: fix warning when submitting superblock in ext4_commit_super()
ext4: add reserved GDT blocks check
Documentation/filesystems/ext4/attributes.rst | 68 +++---
Documentation/filesystems/ext4/bigalloc.rst | 2 +-
Documentation/filesystems/ext4/bitmaps.rst | 6 +-
Documentation/filesystems/ext4/blockgroup.rst | 30 +--
Documentation/filesystems/ext4/blockmap.rst | 2 +-
Documentation/filesystems/ext4/checksums.rst | 26 +--
Documentation/filesystems/ext4/directory.rst | 166 +++++++-------
Documentation/filesystems/ext4/eainode.rst | 10 +-
Documentation/filesystems/ext4/group_descr.rst | 126 +++++------
Documentation/filesystems/ext4/ifork.rst | 60 +++---
Documentation/filesystems/ext4/inlinedata.rst | 8 +-
Documentation/filesystems/ext4/inodes.rst | 306 +++++++++++++-------------
Documentation/filesystems/ext4/journal.rst | 214 +++++++++---------
Documentation/filesystems/ext4/mmp.rst | 36 ++--
Documentation/filesystems/ext4/overview.rst | 2 +-
Documentation/filesystems/ext4/special_inodes.rst | 8 +-
Documentation/filesystems/ext4/super.rst | 550 +++++++++++++++++++++++------------------------
fs/ext4/inode.c | 2 +-
fs/ext4/mballoc.c | 26 ++-
fs/ext4/migrate.c | 2 +-
fs/ext4/namei.c | 3 +-
fs/ext4/page-io.c | 2 +-
fs/ext4/resize.c | 10 +
fs/ext4/super.c | 172 ++++++++-------
fs/ext4/xattr.c | 3 +-
fs/jbd2/transaction.c | 2 +-
26 files changed, 947 insertions(+), 895 deletions(-)
next reply other threads:[~2022-06-19 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 0:30 Theodore Ts'o [this message]
2022-06-19 3:02 ` [GIT PULL] ext4 fixes for 5.19-rc3 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=Yq5uOVSUci3fv+Mw@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