linux-kernel - Re: [PATCH] ASoC: wm_adsp: Don't use no_free_ptr() when passing to PTR

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: <174605351366.3987837.5374259118304157069.b4-ty@kernel.org>
Date: Thu, 01 May 2025 07:51:53 +0900
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] ASoC: wm_adsp: Don't use no_free_ptr() when passing to
 PTR_ERR()

On Mon, 28 Apr 2025 10:08:03 +0100, Richard Fitzgerald wrote:
> It's no longer necessary to no_free_ptr() an auto-freed pointer before
> passing it to PTR_ERR(). This was fixed by commit
> cd7eb8f83fcf ("mm/slab: make __free(kfree) accept error pointers").
> 
> Removing the no_free_ptr() avoids the spurious warning
> "inconsistent IS_ERR and PTR_ERR".
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: wm_adsp: Don't use no_free_ptr() when passing to PTR_ERR()
      commit: 94602d84163c127ec2374fba0fcb6587a07785ce

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