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 5.18-rc4
Date: Fri, 22 Apr 2022 18:31:39 -0400 [thread overview]
Message-ID: <YmMsywgKkOpa6dlR@mit.edu> (raw)
The following changes since commit 919adbfec29d5b89b3e45620653cbeeb0d42e6fd:
ext4: fix kernel doc warnings (2022-03-15 17:45:36 -0400)
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 23e3d7f7061f8682c751c46512718f47580ad8f0:
jbd2: fix a potential race while discarding reserved buffers after an abort (2022-04-21 14:21:30 -0400)
----------------------------------------------------------------
Fix some syzbot-detected bugs, as well as other bugs found by I/O
injection testing. Change ext4's fallocate to update consistently
drop set[ug]id bits when an fallocate operation might possibly change
the user-visible contents of a file. Also, improve handling of
potentially invalid values in the the s_overhead_cluster superblock
field to avoid ext4 returning a negative number of free blocks.
----------------------------------------------------------------
Darrick J. Wong (1):
ext4: fix fallocate to use file_modified to update permissions consistently
Tadeusz Struk (1):
ext4: limit length to bitmap_maxbytes - blocksize in punch_hole
Theodore Ts'o (3):
ext4: fix overhead calculation to account for the reserved gdt blocks
ext4: force overhead calculation if the s_overhead_cluster makes no sense
ext4: update the cached overhead value in the superblock
Ye Bin (4):
ext4: fix symlink file size not match to file content
ext4: fix bug_on in start_this_handle during umount filesystem
ext4: fix use-after-free in ext4_search_dir
jbd2: fix a potential race while discarding reserved buffers after an abort
wangjianjian (C) (1):
ext4, doc: fix incorrect h_reserved size
Documentation/filesystems/ext4/attributes.rst | 2 +-
fs/ext4/ext4.h | 7 ++++++-
fs/ext4/extents.c | 32 +++++++++++++++++++++++++-------
fs/ext4/inode.c | 18 ++++++++++++++++--
fs/ext4/ioctl.c | 16 ++++++++++++++++
fs/ext4/namei.c | 4 ++--
fs/ext4/page-io.c | 4 +++-
fs/ext4/super.c | 40 +++++++++++++++++++++++++++++-----------
fs/jbd2/commit.c | 4 +++-
9 files changed, 101 insertions(+), 26 deletions(-)
next reply other threads:[~2022-04-22 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 22:31 Theodore Ts'o [this message]
2022-04-23 1:20 ` [GIT PULL] ext4 fixes for 5.18-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=YmMsywgKkOpa6dlR@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