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: <fbz7l6ekiqqhi47cv6r2ots7siztdydfcspwr2jt56ldsyxjep@rwd5zx2oezl4>
Date: Mon, 12 Feb 2024 10:55:13 +0100
From: Daniel Wagner <dwagner@...e.de>
To: Fedor Pchelkin <pchelkin@...ras.ru>
Cc: James Smart <james.smart@...adcom.com>, 
	Ram Vegesna <ram.vegesna@...adcom.com>, "James E.J. Bottomley" <jejb@...ux.ibm.com>, 
	"Martin K. Petersen" <martin.petersen@...cle.com>, Hannes Reinecke <hare@...e.de>, linux-scsi@...r.kernel.org, 
	target-devel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Alexey Khoroshilov <khoroshilov@...ras.ru>, lvc-project@...uxtesting.org, stable@...r.kernel.org
Subject: Re: [PATCH v2] scsi: elx: efct: adjust error handling inside
 efct_hw_setup_io

On Sat, Feb 10, 2024 at 02:08:33PM +0300, Fedor Pchelkin wrote:
> IO and WQE buffers are allocated once per HW and can be reused later. If
> WQE buffers allocation fails then the whole allocation is marked as failed
> but already created IO array internal objects are not freed. hw->io is
> freed but not nullified in that specific case - it may become a problem
> later as efct_hw_setup_io() is supposed to be reusable for the same HW.
> 
> Also rollback if HW IO objects initialization loop fails due to memory
> allocation error.
> 
> While at it, use kcalloc instead of kmalloc_array/memset-zero combination
> and get rid of some needless NULL assignments: nullifying hw->io[i]
> elements just before freeing hw->io is not really useful.
> 
> Found by Linux Verification Center (linuxtesting.org).
> 
> Fixes: 4df84e846624 ("scsi: elx: efct: Driver initialization routines")
> Cc: stable@...r.kernel.org
> Suggested-by: Daniel Wagner <dwagner@...e.de>
> Signed-off-by: Fedor Pchelkin <pchelkin@...ras.ru>
> ---
> v2: per Daniel Wagner's notice, handle the other possible memory
>     allocation errors inside the function.

Looks good to me! Thanks!

Reviewed-by: Daniel Wagner <dwagner@...e.de>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ