From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Ebner <c.ebner@proxmox.com>
Cc: dhowells@redhat.com, jlayton@kernel.org, stable@vger.kernel.org,
netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH stable 6.11.y] netfs: reset subreq->iov_iter before netfs_clear_unread() tail clean
Date: Wed, 6 Nov 2024 06:59:03 +0100 [thread overview]
Message-ID: <2024110644-audible-canine-30ca@gregkh> (raw)
In-Reply-To: <20241027114315.730407-1-c.ebner@proxmox.com>
On Sun, Oct 27, 2024 at 12:43:15PM +0100, Christian Ebner wrote:
> Fixes file corruption issues when reading contents via ceph client.
>
> Call netfs_reset_subreq_iter() to align subreq->io_iter before
> calling netfs_clear_unread() to clear tail, as subreq->io_iter count
> and subreq->transferred might not be aligned after incomplete I/O,
> having the subreq's NETFS_SREQ_CLEAR_TAIL set.
>
> Based on ee4cdf7b ("netfs: Speed up buffered reading"), which
> introduces a fix for the issue in mainline.
>
> Fixes: 92b6cc5d ("netfs: Add iov_iters to (sub)requests to describe various buffers")
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=219237
> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
> ---
> Sending this patch in an attempt to backport the fix introduced by
> commit ee4cdf7b ("netfs: Speed up buffered reading"), which however
> can not be cherry picked for older kernels, as the patch is not
> independent from other commits and touches a lot of unrelated (to
> the fix) code.
We would much rather take the original series of commits, what exactly
are they here?
thanks,
greg k-h
next prev parent reply other threads:[~2024-11-06 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 11:43 [PATCH stable 6.11.y] netfs: reset subreq->iov_iter before netfs_clear_unread() tail clean Christian Ebner
2024-11-06 5:59 ` Greg KH [this message]
2024-11-06 8:26 ` Christian Ebner
2024-11-06 8:35 ` Greg KH
2024-11-07 11:51 ` Christian Ebner
2024-11-10 5:08 ` Greg KH
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=2024110644-audible-canine-30ca@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=c.ebner@proxmox.com \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox