linux-kernel - Re: [PATCH] spi: sophgo: fix incorrect type for ret in sg2044_spifmc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <174224057287.315737.14282458820936385729.b4-ty@kernel.org>
Date: Mon, 17 Mar 2025 19:42:52 +0000
From: Mark Brown <broonie@...nel.org>
To: looong.bin@...il.com, Qasim Ijaz <qasdev00@...il.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: sophgo: fix incorrect type for ret in
 sg2044_spifmc_write()

On Thu, 13 Mar 2025 21:45:45 +0000, Qasim Ijaz wrote:
> The sg2044_spifmc_write() function uses 'ret' of unsigned type
> size_t to capture return values from sg2044_spifmc_wait_xfer_size()
> and sg2044_spifmc_wait_int(). Since these functions may return
> negative error codes, using an unsigned type prevents proper
> error detection, as size_t cannot represent negative values.
> 
> Change 'ret' to type int so that negative values are handled correctly.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: sophgo: fix incorrect type for ret in sg2044_spifmc_write()
      commit: 3c9403f150b70d76198e414d53c95e1698e3f99f

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark