From: Christian Ebner <c.ebner@proxmox.com>
To: Greg KH <gregkh@linuxfoundation.org>
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: Thu, 7 Nov 2024 12:51:14 +0100 [thread overview]
Message-ID: <fac697e2-22aa-40e5-942a-a6e40efee0b2@proxmox.com> (raw)
In-Reply-To: <2024110625-blot-uncooked-48f9@gregkh>
On 11/6/24 09:35, Greg KH wrote:
> On Wed, Nov 06, 2024 at 09:26:46AM +0100, Christian Ebner wrote:
>
> Please try testing the original fixes and providing them as a patch
> series and send them for us to review.
>
> thanks,
>
> greg k-h
Hi Greg,
as mentioned, the original series does not apply on stable-6.11.y and
securely and correctly back-porting this is out of scope for us, given
resource and time constraints.
The main intend was to contribute back a patch which is also
back-portable to older kernels. This seems unfeasible with the huge
original patch series. The submitted patch has successfully been tested
on our side and fixes the issue for affected customers which were
willing to test the patch.
Thanks for your time.
Best regards,
Christian Ebner
next prev parent reply other threads:[~2024-11-07 11:51 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
2024-11-06 8:26 ` Christian Ebner
2024-11-06 8:35 ` Greg KH
2024-11-07 11:51 ` Christian Ebner [this message]
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=fac697e2-22aa-40e5-942a-a6e40efee0b2@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).