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: <165005283988.16277.2709789836252162848.b4-ty@ti.com>
Date:   Fri, 15 Apr 2022 15:02:33 -0500
From:   Nishanth Menon <nm@...com>
To:     <kristo@...nel.org>, QintaoShen <unSimple1993@....com>
CC:     Nishanth Menon <nm@...com>, <linux-kernel@...r.kernel.org>,
        <ssantosh@...nel.org>, <d-gerlach@...com>
Subject: Re: [PATCH v1] soc: ti: ti_sci_pm_domains: Check for null return of devm_kcalloc

Hi QintaoShen,

On Thu, 24 Mar 2022 15:44:03 +0800, QintaoShen wrote:
> The allocation funciton devm_kcalloc may fail and return a null pointer,
> which would cause a null-pointer dereference later.
> It might be better to check it and directly return -ENOMEM just like the
> usage of devm_kcalloc in previous code.
> 
> 

I have applied the following to branch ti-drivers-soc-next on [1].
Thank you!

[1/1] soc: ti: ti_sci_pm_domains: Check for null return of devm_kcalloc
      commit: ba56291e297d28aa6eb82c5c1964fae2d7594746

Sidenote: [PATCH] is sufficient for v1 of the patch, it is understood to be
 default indexed from 1 ;). Ofcourse, an update of the patch would have been
 posted as [PATCH V2] and so on..

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant 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.

[1] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ