From: Liang Haowen <nbg2974@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: linux-leds@vger.kernel.org, Pavel Machek <pavel@kernel.org>,
Martin K . Petersen <mkp@kernel.org>,
linux-scsi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Denis Benato <denis.benato@linux.dev>,
Armin Wolf <W_Armin@gmx.de>, Hans de Goede <hansg@kernel.org>,
Ilpo Jarvinen <ilpo.jarvinen@linux.intel.com>,
Marco Scardovi <scardracs@disroot.org>,
sashiko-reviews@lists.linux.dev
Subject: Re: [RFC v9 1/1] leds: asus-aura-scsi: Add ASUS Aura RGB LED driver for ROG NVMe enclosures
Date: Thu, 15 Oct 2026 07:01:46 -0700 (PDT) [thread overview]
Message-ID: <6ad0dcca.e4f0a24b.cac3b.c1fe@mx.google.com> (raw)
In-Reply-To: <20261015115043.GA1863739@google.com>
On Thu, 15 Oct 2026, Lee Jones wrote:
> A driver source file without 'Kconfig' or 'Makefile' integration is dead code in
> the tree. Either wire it up now or hold off on submitting until the rest of the
> pieces are ready.
v10 wires it up: the drivers/leds/rgb/Kconfig and Makefile entries
are in, and the series is posted as a new thread under the same
subject.
Your 25 Sep note never reached me: neither it nor the copy
kernel.org relayed on 14 Oct is in any folder of my mailbox. I
first saw its content today, quoted in this mail. The three week
gap was delivery, not silence; this is my first chance to answer
it.
> Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
> - [Low] leds: asus-aura-scsi: undefined function kzalloc_obj() causes build failure
> - [Low] leds: asus-aura-scsi: blk_rq_map_kern() missing required request_queue argument
> - [Low] leds: asus-aura-scsi: strscpy() called with missing size argument
>
> Was this even tested?
Yes. The driver builds with clang (LLVM=1) against 7.2.4 with zero
warnings, loads on the enclosure, and was exercised today: the four
LED zones driven to independent colours and checked by eye, 60
sequential and 100 concurrent updates, the sdev deleted mid-write
(zero splats, clean detach), rmmod, and a fresh attach through a
host scan.
All three findings assume a tree older than v7.0:
- kzalloc_obj() has existed since v7.0 (Kees Cook's series,
include/linux/slab.h).
- blk_rq_map_kern() takes four arguments on current kernels; the
queue comes from the request itself, and scsi_execute_cmd()
calls it the same way.
- strscpy() with two arguments is backed by __strscpy0 in
include/linux/string.h, which infers sizeof(dst) and rejects
non-array destinations. v10 passes the size explicitly anyway,
since it costs nothing.
kzalloc_obj() has now been reported by the bot in all nine of
its reviews and blk_rq_map_kern() in eight, and the answer has
not changed since the first time. If sashiko could review
against a current tree, or drop those two checks, the noise
would stop.
Best regards,
Liang
prev parent reply other threads:[~2026-10-15 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 13:40 [RFC v9 0/1] leds: asus-aura-scsi: Add ASUS Aura RGB LED driver for ROG NVMe enclosures Liang Haowen
2026-09-25 13:40 ` [RFC v9 1/1] " Liang Haowen
2026-09-25 13:52 ` sashiko-bot
[not found] ` <179198503855.839288.7797731903424311774@kernel.org>
2026-10-15 11:50 ` Lee Jones
2026-10-15 14:01 ` Liang Haowen [this message]
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=6ad0dcca.e4f0a24b.cac3b.c1fe@mx.google.com \
--to=nbg2974@gmail.com \
--cc=W_Armin@gmx.de \
--cc=denis.benato@linux.dev \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@kernel.org \
--cc=pavel@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=scardracs@disroot.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