All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kees Cook" <kees@kernel.org>
Cc: linux-leds@vger.kernel.org, lee@kernel.org
Subject: Re: [PATCH] leds: aat1290: Allocate mm_current_scale with ARRAY_SIZE()
Date: Thu, 17 Sep 2026 21:21:57 +0000	[thread overview]
Message-ID: <20260917212158.482F61F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917211357.i.412-kees@kernel.org>

> From: Kees Cook <kees+treewide@kernel.org>
> 
> In preparation for making the devm_kmalloc family of allocators type
> aware, we need to make sure that the returned type from the allocation
> matches the type of the variable being assigned. (Before, the allocator
> would always return "void *", which can be implicitly cast to any
> pointer type.)
> 
> This allocates one int per entry of max_mm_current_percent, but the size
> was taken from the whole array, which would make the allocation type a
> pointer to the array rather than the "int *" being assigned. Allocate
> ARRAY_SIZE-many entries instead. The resulting allocation size is the
> same: AAT1290_MM_CURRENT_SCALE_SIZE and
> ARRAY_SIZE(max_mm_current_percent) are both 15.
> 
> Build tested ARCH=x86_64 allmodconfig with GCC 16.2.0:
> drivers/leds/flash/leds-aat1290.o
> 
> Assisted-by: LLM coccinelle
> Signed-off-by: Kees Cook <kees+treewide@kernel.org>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260917211357.i.412-kees@kernel.org?part=1


  reply	other threads:[~2026-09-17 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 21:13 [PATCH] leds: aat1290: Allocate mm_current_scale with ARRAY_SIZE() Kees Cook
2026-09-17 21:21 ` sashiko-bot [this message]
2026-09-23  9:56 ` (subset) " Lee Jones

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=20260917212158.482F61F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=kees@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.