public inbox for linux-spi@vger.kernel.org
 help / color / mirror / Atom feed
From: Prajna Rajendra Kumar <prajna.rajendrakumar@microchip.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Mark Brown <broonie@kernel.org>,
	Conor Dooley <conor.dooley@microchip.com>,
	<linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH next v2] spi: Fix potential uninitialized variable in probe()
Date: Mon, 24 Nov 2025 15:00:55 +0000	[thread overview]
Message-ID: <48ad36dc-613f-401f-a8e2-dec832bd6ee1@microchip.com> (raw)
In-Reply-To: <aSQPkfkiJ0w-FJMW@stanley.mountain>

On 24/11/2025 07:56, Dan Carpenter wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> If the device tree is messed up, then potentially the "protocol" string
> could potentially be uninitialized.  The property is supposed to default
> to "motorola" so if the of_property_read_string() function returns
> -EINVAL then default to "motorola".
>
> Fixes: 059f545832be ("spi: add support for microchip "soft" spi controller")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
Reviewed-by: Prajna Rajendra Kumar <prajna.rajendrakumar@microchip.com>
> ---
> v2: Add an error message on failure.
>      Default to "motorola".
>
>   drivers/spi/spi-microchip-core-spi.c | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/spi/spi-microchip-core-spi.c b/drivers/spi/spi-microchip-core-spi.c
> index b8738190cdcb..16e0885474a0 100644
> --- a/drivers/spi/spi-microchip-core-spi.c
> +++ b/drivers/spi/spi-microchip-core-spi.c
> @@ -295,10 +295,10 @@ static int mchp_corespi_transfer_one(struct spi_controller *host,
>
>   static int mchp_corespi_probe(struct platform_device *pdev)
>   {
> +       const char *protocol = "motorola";
>          struct spi_controller *host;
>          struct mchp_corespi *spi;
>          struct resource *res;
> -       const char *protocol;
>          u32 num_cs, mode, frame_size;
>          bool assert_ssel;
>          int ret = 0;
> @@ -320,6 +320,8 @@ static int mchp_corespi_probe(struct platform_device *pdev)
>           */
>          ret = of_property_read_string(pdev->dev.of_node, "microchip,protocol-configuration",
>                                        &protocol);
> +       if (ret && ret != -EINVAL)
> +               return dev_err_probe(&pdev->dev, ret, "Error reading protocol-configuration\n");
>          if (strcmp(protocol, "motorola") != 0)
>                  return dev_err_probe(&pdev->dev, -EINVAL,
>                                       "CoreSPI: protocol '%s' not supported by this driver\n",
> --
> 2.51.0
>


  reply	other threads:[~2025-11-24 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24  7:56 [PATCH next v2] spi: Fix potential uninitialized variable in probe() Dan Carpenter
2025-11-24 15:00 ` Prajna Rajendra Kumar [this message]
2025-11-24 19:15 ` 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=48ad36dc-613f-401f-a8e2-dec832bd6ee1@microchip.com \
    --to=prajna.rajendrakumar@microchip.com \
    --cc=broonie@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=dan.carpenter@linaro.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.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