linux-kernel - Re: [PATCH] ASoC: nau8821: check regmap_raw_read/regmap_raw

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: <172928168672.188041.5557095423095482145.b4-ty@kernel.org>
Date: Fri, 18 Oct 2024 21:01:26 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Vitaliy Shevtsov <v.shevtsov@...ima.ru>
Cc: Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, 
 Seven Lee <wtli@...oton.com>, 
 Uwe Kleine-König <u.kleine-koenig@...gutronix.de>, 
 Andy Shevchenko <andy.shevchenko@...il.com>, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, lvc-project@...uxtesting.org
Subject: Re: [PATCH] ASoC: nau8821: check regmap_raw_read/regmap_raw_write
 for failure

On Fri, 18 Oct 2024 16:07:41 +0500, Vitaliy Shevtsov wrote:
> The return values from both regmap_raw_read() and regmap_raw_write() are not
> checked despite they can fail. Propagate possible errors to caller.
> 
> Found by Linux Verification Center (linuxtesting.org) with Svace.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: nau8821: check regmap_raw_read/regmap_raw_write for failure
      commit: 1b9971a4e01b80afbf061ad7cdf84ac6fbbbde8d

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