From: Eric Biggers <ebiggers@kernel.org>
To: Pooja Trivedi <poojatrivedi@gmail.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: net/tls(TLS_SW): double free in tls_tx_records
Date: Thu, 29 Aug 2019 00:03:28 -0500 [thread overview]
Message-ID: <20190829050328.GA3307@zzz.localdomain> (raw)
In-Reply-To: <CAOrEds=P2nBHa+rqx3SC6fZ97rRCdBWgXkg2N8yYLP8-knfxpw@mail.gmail.com>
On Wed, Aug 28, 2019 at 11:41:25AM -0400, Pooja Trivedi wrote:
> TLS module crash while running SSL record encryption using
> klts_send_[file] using crypto accelerator (Nitrox).
Does the Nitrox crypto driver pass the extra crypto self-tests, which were added
in v5.1 and v5.2? I.e. boot a kernel configured with
CONFIG_CRYPTO_MANAGER_EXTRA_TESTS=y. I'm asking in case this is a bug that's
already detected by the tests, as that could be an easier way for someone to
start fixing this driver... And if you're actually using this driver for
something important, you may want to look into making sure it passes the tests
anyway, as I haven't seen anyone else do so yet.
Otherwise, it could also be a bug in net/tls/ (in which case you'd need to
report it to the maintainers for that), or it could be a bug that only shows up
with multiple concurrent requests, which isn't yet covered by the self-tests.
- Eric
prev parent reply other threads:[~2019-08-29 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOrEdsmpHT-=zH9zyHv=pLX2ENb1S0AnkrcWVgMxqWrxKsF3yw@mail.gmail.com>
[not found] ` <CAOrEdsnpQ+e5rWKxrr4vXH6_4CeESSE27GRcQd4TuXDe72MVmQ@mail.gmail.com>
2019-08-28 15:41 ` net/tls(TLS_SW): double free in tls_tx_records Pooja Trivedi
2019-08-29 5:03 ` Eric Biggers [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=20190829050328.GA3307@zzz.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=poojatrivedi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox