From: Mark Brown <broonie@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Emanuele Ghidoli <ghidoliemanuele@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: soc-core: reset rtd->num_components after allocation
Date: Wed, 11 Nov 2026 13:09:25 +0000 [thread overview]
Message-ID: <853110dc-2ab9-4271-9e81-20ce5068ecc0@sirena.org.uk> (raw)
In-Reply-To: <EAAF07EF-6B11-4EA5-A5AF-A7787CA2F196@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On Tue, Nov 10, 2026 at 09:59:12PM -0800, Kees Cook wrote:
> For example, what keeps snd_soc_rtd_add_component() from overflowing
> that array? If you want to protect the array, add another member, say
> max_component, and use that for the counter, which gets set at
> allocation time and protects the array from indexing beyond the actual
> allocation size.
We could do that, and it'd certainly be good to do so, but anything
that's in a position to do anything here will already have sufficient
access to the system that it can just directly cause issues.
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-11-11 13:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 10:25 Emanuele Ghidoli
2026-11-09 11:07 ` Takashi Iwai
2026-11-10 11:47 ` Takashi Iwai
2026-11-11 5:50 ` Kees Cook
2026-11-11 5:59 ` Kees Cook
2026-11-11 10:28 ` Emanuele Ghidoli
2026-11-12 17:27 ` Kees Cook
2026-11-11 13:09 ` Mark Brown [this message]
2026-11-12 17:33 ` Kees Cook
2026-11-10 9:57 ` Jan Remes
2026-11-10 17:45 ` Mark Brown
2026-11-11 10:06 ` Alexander Stein
2026-11-11 12:26 ` Cosmin-Gabriel Tanislav
2026-11-10 22:01 Rujbin
2026-11-14 8:38 Shawn Guo
2026-11-15 11:42 ` Mark Brown
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=853110dc-2ab9-4271-9e81-20ce5068ecc0@sirena.org.uk \
--to=broonie@kernel.org \
--cc=emanuele.ghidoli@toradex.com \
--cc=ghidoliemanuele@gmail.com \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®