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 update for 6.8-rc1
Date: Wed, 10 Jan 2024 15:35:21 -0500 [thread overview]
Message-ID: <20240110203521.GA1013681@mit.edu> (raw)
The following changes since commit 6c02757c936063f0631b4e43fe156f8c8f1f351f:
jbd2: fix soft lockup in journal_finish_inode_data_buffers() (2023-12-12 10:25:46 -0500)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus-6.8-rc1
for you to fetch changes up to 68da4c44b994aea797eb9821acb3a4a36015293e:
ext4: fix inconsistent between segment fstrim and full fstrim (2024-01-10 13:53:36 -0500)
----------------------------------------------------------------
Various ext4 bug fixes and cleanups for v6.8-rc1. The fixes are
mostly in the fstrim and mballoc code paths. Also enable
dioread_nolock in the case where the block size is less than the page
size. (Dioread_nolock has been default in the bs == ps case for quite
some time.)
----------------------------------------------------------------
Baokun Li (4):
ext4: unify the type of flexbg_size to unsigned int
ext4: remove unnecessary check from alloc_flex_gd()
ext4: avoid online resizing failures due to oversized flex bg
ext4: reduce unnecessary memory allocation in alloc_flex_gd()
Gou Hao (2):
ext4: delete redundant calculations in ext4_mb_get_buddy_page_lock()
ext4: improving calculation of 'fe_{len|start}' in mb_find_extent()
Matthew Wilcox (Oracle) (1):
ext4: convert ext4_da_do_write_end() to take a folio
Ojaswin Mujoo (4):
ext4: enable dioread_nolock as default for bs < ps case
ext4: treat end of range as exclusive in ext4_zero_range()
ext4: clarify handling of unwritten bh in __ext4_block_zero_page_range()
ext4: fallback to complex scan if aligned scan doesn't work
Suraj Jitindar Singh (1):
ext4: allow for the last group to be marked as trimmed
Ye Bin (1):
ext4: fix inconsistent between segment fstrim and full fstrim
Zhihao Cheng (5):
jbd2: add errseq to detect client fs's bdev writeback error
jbd2: replace journal state flag by checking errseq
jbd2: remove unused 'JBD2_CHECKPOINT_IO_ERROR' and 'j_atomic_flags'
jbd2: abort journal when detecting metadata writeback error of fs dev
ext4: move ext4_check_bdev_write_error() into nojournal mode
fs/ext4/ext4_jbd2.c | 5 ++---
fs/ext4/extents.c | 6 ++++--
fs/ext4/inode.c | 25 ++++++++++++++++---------
fs/ext4/mballoc.c | 65 +++++++++++++++++++++++++++++++++++++----------------------------
fs/ext4/resize.c | 49 +++++++++++++++++++++++++++++++++----------------
fs/ext4/super.c | 11 +----------
fs/jbd2/checkpoint.c | 11 -----------
fs/jbd2/journal.c | 11 ++++++-----
fs/jbd2/recovery.c | 7 +------
fs/jbd2/transaction.c | 14 ++++++++++++++
include/linux/jbd2.h | 37 ++++++++++++++++++++++++++-----------
11 files changed, 140 insertions(+), 101 deletions(-)
next reply other threads:[~2024-01-10 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 20:35 Theodore Ts'o [this message]
2024-01-11 2:24 ` [GIT PULL] ext4 update for 6.8-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=20240110203521.GA1013681@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;
as well as URLs for NNTP newsgroup(s).