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 bug fixes for v6.4-rc1
Date: Sun, 30 Apr 2023 14:08:28 -0400 [thread overview]
Message-ID: <20230430180828.GA584597@mit.edu> (raw)
The following changes since commit 519fe1bae7e20fc4e7f179d50b6102b49980e85d:
ext4: Add a uapi header for ext4 userspace APIs (2023-04-19 23:39:42 -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 d4fab7b28e2f5d74790d47a8d298da0abfb5132f:
ext4: clean up error handling in __ext4_fill_super() (2023-04-28 12:56:40 -0400)
----------------------------------------------------------------
Some ext4 regression and bug fixes for -rc1
----------------------------------------------------------------
Nathan Chancellor (1):
ext4: fix unused iterator variable warnings
Theodore Ts'o (3):
ext4: fix lost error code reporting in __ext4_fill_super()
ext4: reflect error codes from ext4_multi_mount_protect() to its callers
ext4: clean up error handling in __ext4_fill_super()
Ye Bin (1):
ext4: fix use-after-free read in ext4_find_extent for bigalloc + inline
Zhihao Cheng (1):
ext4: fix i_disksize exceeding i_size problem in paritally written case
fs/ext4/extents.c | 3 ++-
fs/ext4/inode.c | 3 +++
fs/ext4/mmp.c | 9 ++++++++-
fs/ext4/super.c | 77 +++++++++++++++++++++++++++++++++++++++++++----------------------------------
4 files changed, 56 insertions(+), 36 deletions(-)
next reply other threads:[~2023-04-30 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 18:08 Theodore Ts'o [this message]
2023-05-01 19:25 ` [GIT PULL] ext4 bug fixes for v6.4-rc1 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=20230430180828.GA584597@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.