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 09:35:55 +0100 [thread overview]
Message-ID: <2024110625-blot-uncooked-48f9@gregkh> (raw)
In-Reply-To: <7e364258-e643-4656-9233-f89f1c4b1a66@proxmox.com>
On Wed, Nov 06, 2024 at 09:26:46AM +0100, Christian Ebner wrote:
> On 11/6/24 06:59, Greg KH wrote:
> > We would much rather take the original series of commits, what exactly
> > are they here?
> >
> > thanks,
> >
> > greg k-h
>
> Hello Greg,
> thank you for your reply.
>
> AFAIK the relevant patches for this series are commits 80887f31..ee4cdf7b,
> although the last patch containing the fix does not apply cleanly on the
> current 6.11.y branch.
>
> Please note, I am not very familiar with the code so unsure if all of the
> patches in the series are required for the fix. Maybe David Howells as
> author of the series can provide some more insights?
>
> The patch series introducing the fix is
> https://lore.kernel.org/all/20240814203850.2240469-1-dhowells@redhat.com/
>
> Please let me know how to proceed, thanks!
Please try testing the original fixes and providing them as a patch
series and send them for us to review.
thanks,
greg k-h
next prev parent reply other threads:[~2024-11-06 8:36 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 [this message]
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=2024110625-blot-uncooked-48f9@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;
as well as URLs for NNTP newsgroup(s).