Hi David,
On Thu, Feb 08, 2018 at 03:07:30PM +, David Howells wrote:
> Eric Biggers wrote:
>
> > The X.509 parser mishandles the case where the certificate's signature's
> > hash algorithm is not available in the crypto API. In this case,
> > x509_get_sig_params() doesn't allocate the cert-
-Original Message-
From: linux-crypto-ow...@vger.kernel.org
[mailto:linux-crypto-ow...@vger.kernel.org] On Behalf Of David Miller
Sent: Tuesday, February 20, 2018 9:46 PM
To: Atul Gupta
Cc: davejwat...@fb.com; herb...@gondor.apana.org.au; s...@queasysnail.net;
linux-crypto@vger.kernel.
From: Atul Gupta
Date: Mon, 19 Feb 2018 12:19:41 +0530
> + struct net_device *netdev = NULL;
> +
> + netdev = dev_get_by_index(sock_net(sk), inet->cork.fl.flowi_oif);
No need for an assignment in the variable declaration here.
You immediately set it to something else unconditionally.
>
On 2/20/2018 12:34 PM, Herbert Xu wrote:
> On Mon, Feb 19, 2018 at 01:16:30PM +, Horia Geantă wrote:
>>
>>> And what about ALGIF path from user space ?
>>> What if the user never calls the last sendmsg() which will call
>>> hash_finup() ?
>>>
>> User is expected to follow the rules of the cryp
On Mon, Feb 19, 2018 at 01:16:30PM +, Horia Geantă wrote:
>
> > And what about ALGIF path from user space ?
> > What if the user never calls the last sendmsg() which will call
> > hash_finup() ?
> >
> User is expected to follow the rules of the crypto API.
> Of course, kernel won't (or at lea
