From: sashiko-bot@kernel.org
To: "Ranjan Kumar" <ranjan.kumar@broadcom.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH v1 01/10] mpi3mr: Skip device shutdown during unload per controller configuration
Date: Fri, 26 Jun 2026 12:03:35 +0000 [thread overview]
Message-ID: <20260626120335.A77A91F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260626114109.43685-2-ranjan.kumar@broadcom.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing `le32_to_cpu()` conversion when reading the little-endian `flags` field from `driver_pg1`.
--
commit d356c9ee9428175d4bc2bdb0dd4aaf2c6a81d8bd
Author: Ranjan Kumar <ranjan.kumar@broadcom.com>
mpi3mr: Skip device shutdown during unload per controller configuration
This commit updates the driver to cache the Driver Page 1 configuration
and skip device shutdown requests during driver unload when the controller
requests it.
> diff --git a/drivers/scsi/mpi3mr/mpi3mr_fw.c b/drivers/scsi/mpi3mr/mpi3mr_fw.c
> index 31b19ed1528e5..eb730318db474 100644
> --- a/drivers/scsi/mpi3mr/mpi3mr_fw.c
> +++ b/drivers/scsi/mpi3mr/mpi3mr_fw.c
[ ... ]
> static void
> -mpi3mr_read_tsu_interval(struct mpi3mr_ioc *mrioc)
> +mpi3mr_read_driver_page1(struct mpi3mr_ioc *mrioc)
> {
> struct mpi3_driver_page1 driver_pg1;
> u16 pg_sz = sizeof(driver_pg1);
> int retval = 0;
>
> mrioc->ts_update_interval = MPI3MR_TSUPDATE_INTERVAL;
> + mrioc->skip_dev_shutdown_on_unload = 0;
>
> retval = mpi3mr_cfg_get_driver_pg1(mrioc, &driver_pg1, pg_sz);
> - if (!retval && driver_pg1.time_stamp_update)
> +
> + if (retval)
> + return;
> +
> + if (driver_pg1.time_stamp_update)
> mrioc->ts_update_interval = (driver_pg1.time_stamp_update * 60);
> +
> + mrioc->skip_dev_shutdown_on_unload =
> + (driver_pg1.flags &
> + MPI3_DRIVER1_FLAGS_DEVICE_SHUTDOWN_ON_UNLOAD_DISABLE) ? 1 : 0;
[Severity: Medium]
Does this bitwise operation need an endian conversion?
Since driver_pg1.flags is an __le32, evaluating it with a bitwise AND
without conversion on a big-endian system will check the wrong byte.
This might cause the feature to silently fail to activate.
Could this use le32_to_cpu(driver_pg1.flags) before the bitwise AND?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260626114109.43685-1-ranjan.kumar@broadcom.com?part=1
next prev parent reply other threads:[~2026-06-26 12:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 11:40 [PATCH v1 00/10] mpi3mr: Few Enhancements and minor fixes Ranjan Kumar
2026-06-26 11:41 ` [PATCH v1 01/10] mpi3mr: Skip device shutdown during unload per controller configuration Ranjan Kumar
2026-06-26 12:03 ` sashiko-bot [this message]
2026-06-26 11:41 ` [PATCH v1 02/10] mpi3mr: Update MPI Headers to revision 41 Ranjan Kumar
2026-06-26 12:07 ` sashiko-bot
2026-06-26 11:41 ` [PATCH v1 03/10] mpi3mr: Add early timestamp synchronization after driver load Ranjan Kumar
2026-06-26 11:41 ` [PATCH v1 04/10] mpi3mr: Fix NVMe page size caching for non-operational devices Ranjan Kumar
2026-06-26 12:07 ` sashiko-bot
2026-06-26 11:41 ` [PATCH v1 05/10] mpi3mr: Fix performance regression caused by extended IRQ poll sleep Ranjan Kumar
2026-06-26 12:02 ` sashiko-bot
2026-06-26 11:41 ` [PATCH v1 06/10] mpi3mr: Fix memory leak on operational queue creation failure Ranjan Kumar
2026-06-26 12:02 ` sashiko-bot
2026-06-26 11:41 ` [PATCH v1 07/10] mpi3mr: Fix firmware event reference leak during cleanup Ranjan Kumar
2026-06-26 12:03 ` sashiko-bot
2026-06-26 11:41 ` [PATCH v1 08/10] mpi3mr: Fix SAS port allocation and registration error handling Ranjan Kumar
2026-06-26 12:06 ` sashiko-bot
2026-06-26 11:41 ` [PATCH v1 09/10] mpi3mr: Fix SAS PHY cleanup in host addition error paths Ranjan Kumar
2026-06-26 12:16 ` sashiko-bot
2026-06-26 11:41 ` [PATCH v1 10/10] mpi3mr: Driver version update to 8.18.0.8.50 Ranjan Kumar
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=20260626120335.A77A91F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ranjan.kumar@broadcom.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox