[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180321151011.GB92320@davejwatson-mba.local>
Date: Wed, 21 Mar 2018 08:10:11 -0700
From: Dave Watson <davejwatson@...com>
To: Boris Pismenny <borisp@...lanox.com>
CC: "David S. Miller" <davem@...emloft.net>,
Tom Herbert <tom@...ntonium.net>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
<herbert@...dor.apana.org.au>, <linux-crypto@...r.kernel.org>,
<netdev@...r.kernel.org>, Atul Gupta <atul.gupta@...lsio.com>,
Vakul Garg <vakul.garg@....com>,
Hannes Frederic Sowa <hannes@...essinduktion.org>,
Steffen Klassert <steffen.klassert@...unet.com>,
John Fastabend <john.fastabend@...il.com>,
Daniel Borkmann <daniel@...earbox.net>
Subject: Re: [PATCH net-next 5/6] tls: RX path for ktls
On 03/21/18 07:20 AM, Boris Pismenny wrote:
>
>
> On 3/20/2018 7:54 PM, Dave Watson wrote:
> > + ctx->control = header[0];
> > +
> > + data_len = ((header[4] & 0xFF) | (header[3] << 8));
> > +
> > + cipher_overhead = tls_ctx->rx.tag_size + tls_ctx->rx.iv_size;
> > +
> > + if (data_len > TLS_MAX_PAYLOAD_SIZE + cipher_overhead) {
> > + ret = -EMSGSIZE;
> > + goto read_failure;
> > + }
> > + if (data_len < cipher_overhead) {
> > + ret = -EMSGSIZE;
>
> I think this should be considered EBADMSG, because this error is cipher
> dependent. At least, that's what happens within OpenSSL. Also, EMSGSIZE is
> usually used only for too long messages.
Ah, indeed. Thanks, will send v2.
Powered by blists - more mailing lists