From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: jakub.kicinski@netronome.com
Subject: various TLS bug fixes...
Date: Tue, 20 Aug 2019 16:05:17 -0700 (PDT) [thread overview]
Message-ID: <20190820.160517.617004656524634921.davem@davemloft.net> (raw)
Jakub,
I just did a batch of networking -stable submissions, however I ran
into some troubles with the various TLS backports.
I was able to backport commit 414776621d10 ("net/tls: prevent
skb_orphan() from leaking TLS plain text with offload") to v5.2
but not to v4.19
I was not able to backport neither d85f01775850 ("net: tls, fix
sk_write_space NULL write when tx disabled") nor commit 57c722e932cf
("net/tls: swap sk_write_space on close") to any release. It seems
like there are a bunch of dependencies and perhaps other fixes.
I suspect you've triaged through this already on your side for other
reasons, so perhaps you could help come up with a sane set of TLS
bug fix backports that would be appropriate for -stable?
Thanks!
next reply other threads:[~2019-08-20 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 23:05 David Miller [this message]
2019-08-21 0:24 ` various TLS bug fixes Jakub Kicinski
2019-08-21 5:18 ` John Fastabend
2019-08-21 6:51 ` Jakub Kicinski
2019-08-21 18:03 ` Jakub Kicinski
2019-08-21 22:55 ` Jakub Kicinski
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=20190820.160517.617004656524634921.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@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).