From: sashiko-bot@kernel.org
To: "Julian Sun" <sunjunchao@bytedance.com>, linux-ext4@vger.kernel.org
Cc: tytso@mit.edu
Subject: Re: [PATCH v2 1/6] ext4: move extent mapping error handling out of the loop
Date: Fri, 23 Oct 2026 06:27:09 +0000 [thread overview]
Message-ID: <sashiko-outbox-182349@kernel.org> (raw)
In-Reply-To: <20261023061851.45579-2-sunjunchao@bytedance.com>
> Move the error handling for mpage_map_one_extent() failures after the
> mapping loop in mpage_map_and_submit_extent(). Keep buffer-processing
> errors on the existing update_disksize path and preserve progress
> tracking and return values.
>
> This prepares for reusing partial-folio submission when buffer processing
> fails. No functional change.
>
> Signed-off-by: Julian Sun <sunjunchao@bytedance.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261023061851.45579-1-sunjunchao@bytedance.com?part=1
next prev parent reply other threads:[~2026-10-23 6:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 6:18 [PATCH v2 0/6] ext4: fix buffered writeback error handling Julian Sun
2026-10-23 6:18 ` [PATCH v2 1/6] ext4: move extent mapping error handling out of the loop Julian Sun
2026-10-23 6:27 ` sashiko-bot [this message]
2026-10-23 6:18 ` [PATCH v2 2/6] ext4: submit mapped buffers when io_end_vec allocation fails Julian Sun
2026-10-23 6:33 ` sashiko-bot
2026-10-23 6:18 ` [PATCH v2 3/6] ext4: prevent stale data exposure after fatal mapping errors Julian Sun
2026-10-23 6:18 ` [PATCH v2 4/6] ext4: put folio on partial writeback validation failure Julian Sun
2026-10-23 6:28 ` sashiko-bot
2026-10-23 6:18 ` [PATCH v2 5/6] ext4: report unwritten extent conversion errors to fsync Julian Sun
2026-10-23 6:26 ` sashiko-bot
2026-10-23 6:18 ` [PATCH v2 6/6] ext4: use atomic bitops for io_end flags Julian Sun
2026-10-23 6:31 ` sashiko-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=sashiko-outbox-182349@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sunjunchao@bytedance.com \
--cc=tytso@mit.edu \
/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