From: sashiko-bot@kernel.org
To: "Dave Jiang" <dave.jiang@intel.com>
Cc: linux-cxl@vger.kernel.org
Subject: Re: [PATCH v3 1/6] cxl/test: Add test for module parameters
Date: Wed, 10 Jun 2026 22:32:05 +0000 [thread overview]
Message-ID: <20260610223205.9DB451F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260610222328.2272427-2-dave.jiang@intel.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The function `have_multiple_modparms()` fails to check the `hmem_test` module parameter, allowing multiple test parameters to be activated simultaneously.
- [Low] The newly added function `have_multiple_modparms` is missing the `static` modifier, making it globally visible.
--
commit a298e853a144eb87f633b800d6fcf071d2088371
Author: Dave Jiang <dave.jiang@intel.com>
cxl/test: Add test for module parameters
This commit adds a test during module initialization to ensure that only
a single module parameter is activated at a time.
> diff --git a/tools/testing/cxl/test/cxl.c b/tools/testing/cxl/test/cxl.c
> index 296516eecfd6a..b00f5161b5f0c 100644
> --- a/tools/testing/cxl/test/cxl.c
> +++ b/tools/testing/cxl/test/cxl.c
> @@ -1814,11 +1814,29 @@ static struct attribute *cxl_acpi_attrs[] = {
> };
> ATTRIBUTE_GROUPS(cxl_acpi);
>
> +bool __init have_multiple_modparms(void)
[Severity: Low]
Should this function be declared static? It appears to only be used locally
within this file, and omitting the static keyword exports it to the global
namespace, which might trigger missing-prototype compiler warnings.
> +{
> + int count = 0;
> +
> + if (interleave_arithmetic)
> + count++;
> + if (extended_linear_cache)
> + count++;
> + if (fail_autoassemble)
> + count++;
[Severity: Medium]
Does this check miss the hmem_test parameter? The cxl_test module is built
from both cxl.c and hmem_test.c, and hmem_test.c defines its own parameter.
It seems a user could load the module with hmem_test=1 and one of the local
parameters (like extended_linear_cache=1) concurrently, bypassing this check.
> +
> + return count > 1;
> +}
> +
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260610222328.2272427-1-dave.jiang@intel.com?part=1
next prev parent reply other threads:[~2026-06-10 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 22:23 [PATCH v3 0/6] cxl: Add CXL type2 accelerator support for cxl_test Dave Jiang
2026-06-10 22:23 ` [PATCH v3 1/6] cxl/test: Add test for module parameters Dave Jiang
2026-06-10 22:32 ` sashiko-bot [this message]
2026-06-10 22:23 ` [PATCH v3 2/6] cxl/test: Add type2 support for mock CFMWS0 Dave Jiang
2026-06-10 22:32 ` sashiko-bot
2026-06-10 22:23 ` [PATCH v3 3/6] cxl/test: Refactor platform device enumerations Dave Jiang
2026-06-10 22:32 ` sashiko-bot
2026-06-10 22:23 ` [PATCH v3 4/6] cxl/test: Add hierarchy enumeration support for type2 device Dave Jiang
2026-06-10 22:36 ` sashiko-bot
2026-06-10 22:23 ` [PATCH v3 5/6] cxl/test: Fixup hdm init for auto region to support type2 Dave Jiang
2026-06-10 22:23 ` [PATCH v3 6/6] cxl/test: Add cxl_test accelerator driver Dave Jiang
2026-06-10 22:37 ` sashiko-bot
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=20260610223205.9DB451F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@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.