From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
Linux Kernel Developers List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ext4 bug fixes for v6.8-rc3
Date: Sun, 4 Feb 2024 00:15:24 -0500 [thread overview]
Message-ID: <20240204051524.GA206753@mit.edu> (raw)
The following changes since commit 0d19d9e14687ff6f43d6c4806ace9ff682d7703f:
Merge tag 'ext4_for_linus-6.8-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2024-01-10 16:09:14 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/for-linus-6.8-rc3
for you to fetch changes up to ec9d669eba4c276d00af88951947fe0e82a6b84c:
ext4: make ext4_set_iomap() recognize IOMAP_DELALLOC map type (2024-02-01 23:59:21 -0500)
----------------------------------------------------------------
Miscellaneous bug fixes and cleanups in ext4's multi-block allocator
and extent handling code.
----------------------------------------------------------------
Baokun Li (8):
ext4: fix double-free of blocks due to wrong extents moved_len
ext4: do not trim the group with corrupted block bitmap
ext4: regenerate buddy after block freeing failed if under fc replay
ext4: avoid bb_free and bb_fragments inconsistency in mb_free_blocks()
ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap corrupt
ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found()
ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()
ext4: mark the group block bitmap as corrupted before reporting an error
Kemeng Shi (9):
ext4: remove unused return value of __mb_check_buddy
ext4: remove unused parameter ngroup in ext4_mb_choose_next_group_*()
ext4: remove unneeded return value of ext4_mb_release_context
ext4: remove unused ext4_allocation_context::ac_groups_considered
ext4: remove unused return value of ext4_mb_release
ext4: remove unused return value of ext4_mb_release_inode_pa
ext4: remove unused return value of ext4_mb_release_group_pa
ext4: remove unnecessary parameter "needed" in ext4_discard_preallocations
ext4: remove 'needed' in trace_ext4_discard_preallocations
Zhang Yi (6):
ext4: refactor ext4_da_map_blocks()
ext4: convert to exclusive lock while inserting delalloc extents
ext4: correct the hole length returned by ext4_map_blocks()
ext4: add a hole extent entry in cache after punch
ext4: make ext4_map_blocks() distinguish delalloc only extent
ext4: make ext4_set_iomap() recognize IOMAP_DELALLOC map type
fs/ext4/ext4.h | 8 +--
fs/ext4/extents.c | 124 ++++++++++++++++++++++++++++-----------------
fs/ext4/file.c | 2 +-
fs/ext4/indirect.c | 2 +-
fs/ext4/inode.c | 90 +++++++++++----------------------
fs/ext4/ioctl.c | 2 +-
fs/ext4/mballoc.c | 140 ++++++++++++++++++++++++++++-----------------------
fs/ext4/mballoc.h | 1 -
fs/ext4/move_extent.c | 10 ++--
fs/ext4/super.c | 2 +-
include/trace/events/ext4.h | 11 ++--
11 files changed, 203 insertions(+), 189 deletions(-)
next reply other threads:[~2024-02-04 5:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 5:15 Theodore Ts'o [this message]
2024-02-04 7:44 ` [GIT PULL] ext4 bug fixes for v6.8-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=20240204051524.GA206753@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.