From: Maxim Mikityanskiy <maximmi@nvidia.com>
To: Boris Pismenny <borisp@nvidia.com>,
John Fastabend <john.fastabend@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Aviad Yehezkel" <aviadye@nvidia.com>
Cc: Tariq Toukan <tariqt@nvidia.com>, <netdev@vger.kernel.org>,
"Maxim Mikityanskiy" <maximmi@nvidia.com>
Subject: [PATCH net 0/2] Fix use-after-free after the TLS device goes down and up
Date: Mon, 24 May 2021 15:12:18 +0300 [thread overview]
Message-ID: <20210524121220.1577321-1-maximmi@nvidia.com> (raw)
This small series fixes a use-after-free bug in the TLS offload code.
The first patch is a preparation for the second one, and the second is
the fix itself.
Maxim Mikityanskiy (2):
net/tls: Replace TLS_RX_SYNC_RUNNING with RCU
net/tls: Fix use-after-free after the TLS device goes down and up
include/net/tls.h | 10 +++++-
net/tls/tls_device.c | 60 ++++++++++++++++++++++++++++-------
net/tls/tls_device_fallback.c | 8 +++++
net/tls/tls_main.c | 1 +
4 files changed, 67 insertions(+), 12 deletions(-)
--
2.25.1
next reply other threads:[~2021-05-24 12:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 12:12 Maxim Mikityanskiy [this message]
2021-05-24 12:12 ` [PATCH net 1/2] net/tls: Replace TLS_RX_SYNC_RUNNING with RCU Maxim Mikityanskiy
2021-05-24 16:05 ` Jakub Kicinski
2021-05-25 8:52 ` Maxim Mikityanskiy
2021-05-25 17:14 ` Jakub Kicinski
2021-05-24 12:12 ` [PATCH net 2/2] net/tls: Fix use-after-free after the TLS device goes down and up Maxim Mikityanskiy
2021-05-24 16:15 ` Jakub Kicinski
2021-05-25 8:52 ` Maxim Mikityanskiy
2021-05-25 17:21 ` Jakub Kicinski
2021-05-25 17:39 ` Jakub Kicinski
2021-05-28 12:40 ` Maxim Mikityanskiy
2021-05-28 19:44 ` Jakub Kicinski
2021-05-31 11:09 ` Maxim Mikityanskiy
2021-06-01 4:16 ` 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=20210524121220.1577321-1-maximmi@nvidia.com \
--to=maximmi@nvidia.com \
--cc=aviadye@nvidia.com \
--cc=borisp@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tariqt@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.