From: "Theodore Ts'o" <tytso@mit.edu>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: [GIT PULL] ext4 fixes for 5.15-rc4
Date: Sun, 3 Oct 2021 12:31:07 -0400 [thread overview]
Message-ID: <YVnay/TJEr8K64+U@mit.edu> (raw)
The following changes since commit baaae979b112642a41b71c71c599d875c067d257:
ext4: make the updating inode data procedure atomic (2021-08-30 23:36:51 -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 f2c77973507fd116c3657df1dc048864a2b16a1c:
ext4: recheck buffer uptodate bit under buffer lock (2021-10-01 00:10:28 -0400)
----------------------------------------------------------------
Fix a number of ext4 bugs in fast_commit, inline data, and delayed
allocation. Also fix error handling code paths in ext4_dx_readdir()
and ext4_fill_super(). Finally, avoid a grabbing a journal head in
the delayed allocation write in the common cases where we are
overwriting an pre-existing block or appending to an inode.
----------------------------------------------------------------
Eric Whitney (2):
ext4: remove extent cache entries when truncating inline data
ext4: enforce buffer head state assertion in ext4_da_map_blocks
Hou Tao (1):
ext4: limit the number of blocks in one ADD_RANGE TLV
Jeffle Xu (1):
ext4: fix reserved space counter leakage
Ritesh Harjani (1):
ext4: fix loff_t overflow in ext4_max_bitmap_size()
Theodore Ts'o (2):
ext4: add error checking to ext4_ext_replay_set_iblocks()
Merge branch 'delalloc-buffer-write' into dev
Zhang Yi (5):
ext4: check and update i_disksize properly
ext4: correct the error path of ext4_write_inline_data_end()
ext4: factor out write end code of inline file
ext4: drop unnecessary journal handle in delalloc write
ext4: recheck buffer uptodate bit under buffer lock
yangerkun (2):
ext4: flush s_error_work before journal destroy in ext4_fill_super
ext4: fix potential infinite loop in ext4_dx_readdir()
fs/ext4/dir.c | 6 +-
fs/ext4/ext4.h | 3 -
fs/ext4/extents.c | 19 ++++--
fs/ext4/fast_commit.c | 6 ++
fs/ext4/inline.c | 150 +++++++++++++++++++++++++--------------------
fs/ext4/inode.c | 176 ++++++++++++++++++-----------------------------------
fs/ext4/super.c | 21 +++++--
7 files changed, 182 insertions(+), 199 deletions(-)
next reply other threads:[~2021-10-03 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 16:31 Theodore Ts'o [this message]
2021-10-03 21:00 ` [GIT PULL] ext4 fixes for 5.15-rc4 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=YVnay/TJEr8K64+U@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