From: Jakub Kicinski <kuba@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: stable@vger.kernel.org, valis <sec@valis.email>,
Simon Horman <horms@kernel.org>,
Sabrina Dubroca <sd@queasysnail.net>,
"David S . Miller" <davem@davemloft.net>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1 1/1] tls: fix race between tx work scheduling and socket close
Date: Thu, 7 Mar 2024 09:14:20 -0800 [thread overview]
Message-ID: <20240307091420.1c09dd0e@kernel.org> (raw)
In-Reply-To: <20240307170959.GO86322@google.com>
On Thu, 7 Mar 2024 17:09:59 +0000 Lee Jones wrote:
> > The 5.15 / 5.10 / 5.4 fixes won't be effective, tho. I don't see
> > commit aec7961916f3f9e88766 in the other LTS branches. Without that
> > (it's still correct but) it doesn't fix the problem, because we still
> > touch the context after releasing the reference (unlocking the spin
> > lock).
>
> No problem.
>
> Should I accompany aec7961916f3 with this fix into the aforementioned
> branches then? Would that then be effective?
Yes, (and c57ca512f3b68d, that's all the pre-req, I think.)
Tho, it may be a more tedious backport.
FWIW tools/testing/selftests/net/tls.c should be relatively solid.
next prev parent reply other threads:[~2024-03-07 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 15:59 [PATCH 6.1 1/1] tls: fix race between tx work scheduling and socket close Lee Jones
2024-03-07 17:08 ` Jakub Kicinski
2024-03-07 17:09 ` Lee Jones
2024-03-07 17:14 ` Jakub Kicinski [this message]
2024-08-02 11:39 ` [PATCH 5.15.y] " Harshit Mogalapalli
2024-08-13 10:39 ` Greg Kroah-Hartman
2024-08-02 11:35 ` [PATCH 6.1 1/1] " Harshit Mogalapalli
2024-03-27 14:35 ` Greg KH
2024-03-27 14:42 ` Lee Jones
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=20240307091420.1c09dd0e@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=horms@kernel.org \
--cc=lee@kernel.org \
--cc=sashal@kernel.org \
--cc=sd@queasysnail.net \
--cc=sec@valis.email \
--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).