From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
Gregg Leventhal <gleventhal@janestreet.com>,
Eric Hagberg <ehagberg@janestreet.com>,
Brian Foster <bfoster@redhat.com>
Subject: Re: [PATCH 6.12.y] iomap: don't revert iov_iter on partially completed buffered writes
Date: Fri, 12 Jun 2026 20:20:33 -0400 [thread overview]
Message-ID: <20260612233100.1-1-sashal@kernel.org> (raw)
In-Reply-To: <20260612121047.397754-1-bfoster@redhat.com>
On Fri, Jun 12, 2026 at 08:10:47AM -0400, Brian Foster wrote:
> Finally, note that I'm not intimately familiar with -stable process so
> I'm just sending a 6.12.y version here. Earlier branches can either also
> include this, revert 18e419f6e80a directly, or I can post targeted
> patches if needed. Thoughts, reviews, flames appreciated.
Queued for 6.12.y, 6.6.y and 6.1.y. Thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2026-06-13 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 12:10 [PATCH 6.12.y] iomap: don't revert iov_iter on partially completed buffered writes Brian Foster
2026-06-13 0:20 ` Sasha Levin [this message]
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=20260612233100.1-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=bfoster@redhat.com \
--cc=ehagberg@janestreet.com \
--cc=gleventhal@janestreet.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@vger.kernel.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.