All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suraj Sonawane <surajsonawane0215@gmail.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: tharunkumar.pasumarthi@microchip.com,
	kumaravel.thiagarajan@microchip.com,
	UNGLinuxDriver@microchip.com, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: busses: fix uninit-value in pci1xxxx_i2c_xfer
Date: Sat, 26 Oct 2024 13:09:41 +0530	[thread overview]
Message-ID: <771b8d5a-f0a9-4d82-bb59-5fdd1fe7447a@gmail.com> (raw)
In-Reply-To: <2nyxcv7yearclljgnqrrrobburq7cvqog46ct56lvtn4zux6z7@twxxpmbuce3c>

On 24/10/24 04:32, Andi Shyti wrote:
> Hi Suraj,
> 
> Thanks for your patch, but...
> 
> On Wed, Oct 23, 2024 at 12:38:45AM +0530, Suraj Sonawane wrote:
>> Fix an issue reported by the smatch static analysis tool:
>> drivers/i2c/busses/i2c-mchp-pci1xxxx.c:1030 pci1xxxx_i2c_xfer() error:
>> uninitialized symbol 'retval'.
>>
>> The error occurs because retval may be used without being set if the
>> transfer loop does not execute (e.g., when num is 0). This could cause
>> the function to return an undefined value, leading to unpredictable
>> behavior.
> 
> ... if num is '0', then we would never reach here, check
> __i2c_transfer().
> 
> Thanks,
> Andi
> 
>> Initialize retval to 0 before the transfer loop to ensure that the
>> function returns a valid value even if no transfers are processed. This
>> change also preserves proper error handling within the loop.
>>
>> Signed-off-by: Suraj Sonawane <surajsonawane0215@gmail.com>
Thank you for reviewing and clarifying.

Best regards,
Suraj Sonawane

      reply	other threads:[~2024-10-26  7:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 19:08 [PATCH] i2c: busses: fix uninit-value in pci1xxxx_i2c_xfer Suraj Sonawane
2024-10-23 23:02 ` Andi Shyti
2024-10-26  7:39   ` Suraj Sonawane [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=771b8d5a-f0a9-4d82-bb59-5fdd1fe7447a@gmail.com \
    --to=surajsonawane0215@gmail.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andi.shyti@kernel.org \
    --cc=kumaravel.thiagarajan@microchip.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tharunkumar.pasumarthi@microchip.com \
    /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.