[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2533674.mvXUDI8C0e@positron.chronox.de>
Date: Sun, 07 Jun 2020 15:07:34 +0200
From: Stephan Müller <smueller@...onox.de>
To: Eric Biggers <ebiggers@...nel.org>
Cc: Dan Carpenter <dan.carpenter@...cle.com>, davem@...emloft.net,
herbert@...dor.apana.org.au, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
syzbot <syzbot+2e635807decef724a1fa@...kaller.appspotmail.com>
Subject: Re: [PATCH v2] crypto: DRBG - always try to free Jitter RNG instance
Am Freitag, 5. Juni 2020, 18:21:49 CEST schrieb Eric Biggers:
Hi Eric,
> To be concrete, I'm suggesting:
>
> if (!IS_ERR_OR_NULL(drbg->jent))
> crypto_free_rng(drbg->jent);
> drbg->jent = NULL;
I currently do not see that this could lead to an issue. But you are right, we
should use defensive programming everywhere.
I will send a v3 shortly.
Thanks.
Ciao
Stephan
Powered by blists - more mailing lists