From: John Fastabend <john.fastabend@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jann Horn <jannh@google.com>
Cc: John Fastabend <john.fastabend@gmail.com>,
stable <stable@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Boris Pismenny <borisp@nvidia.com>
Subject: Re: [missing stable fix on 5.x] [PATCH] net: tls, update curr on splice as well
Date: Mon, 08 Jan 2024 16:50:19 -0800 [thread overview]
Message-ID: <659c984bb4200_a3a72084@john.notmuch> (raw)
In-Reply-To: <2024010822-clinking-kangaroo-e8fa@gregkh>
Greg Kroah-Hartman wrote:
> On Mon, Jan 08, 2024 at 02:10:31PM +0100, Jann Horn wrote:
> > On Thu, Dec 14, 2023 at 8:45 PM John Fastabend <john.fastabend@gmail.com> wrote:
> > > commit c5a595000e2677e865a39f249c056bc05d6e55fd upstream.
> > >
> > > Backport of upstream fix for tls on 6.1 and lower kernels.
> > > The curr pointer must also be updated on the splice similar to how
> > > we do this for other copy types.
> > >
> > > Cc: stable@vger.kernel.org # 6.1.x-
> >
> > I think this Cc marker was wrong - the commit message says "on 6.1 and
> > lower kernels", but this marker seems to say "6.1 and *newer*
> > kernels". The current status is that this issue is fixed on 6.6.7 and
> > 6.1.69, but not on the 5.x stable kernels.
>
> Then can someone provide a working backport to those kernels? Right
> now, this one does not apply at all there.
I'll put something together now and run it through some tests then
send it. I'm not sure where I got the notation 6.1.x- to mean <=6.1,
but I don't see it in the stable-kernel-rules.rst at the moment
so maybe I made it up. Sorry about that.
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2024-01-09 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 19:45 [PATCH] net: tls, update curr on splice as well John Fastabend
2024-01-08 13:10 ` [missing stable fix on 5.x] " Jann Horn
2024-01-08 14:07 ` Greg Kroah-Hartman
2024-01-09 0:50 ` John Fastabend [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=659c984bb4200_a3a72084@john.notmuch \
--to=john.fastabend@gmail.com \
--cc=borisp@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=kuba@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox