From: Sasha Levin <sasha.levin@oracle.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
"open list:CRYPTO API" <linux-crypto@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: crypto: algif_hash: creating 0 sized array in hash_accept
Date: Tue, 26 Jan 2016 09:30:54 -0500 [thread overview]
Message-ID: <56A7831E.5020208@oracle.com> (raw)
In-Reply-To: <20160126140724.GA22685@gondor.apana.org.au>
On 01/26/2016 09:07 AM, Herbert Xu wrote:
> On Tue, Jan 26, 2016 at 08:26:41AM -0500, Sasha Levin wrote:
>> >
>> > This seems to be happening with "digest_null".
> In that case this is expected as digest_null obviously has no
> state. So why is a zero-length array disallowed by ubsan?
The C spec forbids it, so ubsan complains :)
Thanks,
Sasha
next prev parent reply other threads:[~2016-01-26 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 12:14 crypto: algif_hash: creating 0 sized array in hash_accept Sasha Levin
2016-01-25 13:58 ` Herbert Xu
2016-01-26 13:26 ` Sasha Levin
2016-01-26 14:07 ` Herbert Xu
2016-01-26 14:30 ` Sasha Levin [this message]
2016-01-26 14:46 ` Herbert Xu
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=56A7831E.5020208@oracle.com \
--to=sasha.levin@oracle.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).