From: Eric Biggers <ebiggers@kernel.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: jason@zx2c4.com, ardb+git@google.com, ardb@kernel.org,
arnd@arndb.de, kees@kernel.org, linux-crypto@vger.kernel.org,
torvalds@linux-foundation.org,
Aaron Ballman <aaron@aaronballman.com>
Subject: Re: [RFC PATCH] libcrypto/chachapoly: Use strict typing for fixed size array arguments
Date: Tue, 2 Dec 2025 16:49:49 +0000 [thread overview]
Message-ID: <20251202164949.GB1638706@google.com> (raw)
In-Reply-To: <uqtp7y4smylm475jfn6krdvib66mjgxavnr5c6ciznslkwdlhd@k3awdazxphqt>
On Tue, Dec 02, 2025 at 02:42:13PM +0100, Alejandro Colomar wrote:
> > Clang doesn't enforce it. Clang doesn't even enforce [static n].
> > Clang is in fact quite bad at diagnosing array bounds violations.
> > Aaron, could you please fix this in Clang?
>
> Self-correction: Actually, there's different enforcement in one case:
Right, and it's the case that actually matters, which is kind of the
point. Maybe you missed the earlier discussions.
- Eric
next prev parent reply other threads:[~2025-12-02 16:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 18:07 [RFC PATCH] libcrypto/chachapoly: Use strict typing for fixed size array arguments Ard Biesheuvel
2025-11-14 20:23 ` Jason A. Donenfeld
2025-11-14 20:33 ` Ard Biesheuvel
2025-11-15 2:14 ` Eric Biggers
2025-11-15 17:11 ` Linus Torvalds
2025-11-15 17:32 ` Linus Torvalds
2025-11-15 17:39 ` Jason A. Donenfeld
2025-12-02 1:12 ` Alejandro Colomar
2025-12-02 1:57 ` Eric Biggers
2025-12-02 10:14 ` Alejandro Colomar
2025-12-02 13:42 ` Alejandro Colomar
2025-12-02 16:49 ` Eric Biggers [this message]
2025-12-02 21:27 ` Alejandro Colomar
2025-12-03 17:24 ` Daniel Thompson
2025-12-03 18:01 ` Alejandro Colomar
2025-12-05 13:59 ` Daniel Thompson
2025-12-13 20:04 ` Alejandro Colomar
2025-11-16 13:57 ` kernel test robot
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=20251202164949.GB1638706@google.com \
--to=ebiggers@kernel.org \
--cc=aaron@aaronballman.com \
--cc=alx@kernel.org \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=jason@zx2c4.com \
--cc=kees@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.