linux-kernel - Re: [PATCH 3/3] mpt3sas, mpt2sas: fix scsi_add_host error handling problems in _scsih

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]

Date:	Fri, 18 Jul 2014 11:46:49 +0200
From:	Christoph Hellwig <hch@....de>
To:	Robert Elliott <elliott@...com>
Cc:	axboe@...nel.dk, abhijit.mahajan@...gotech.com, kmo@...arainc.com,
	nagalakshmi.nandigama@...gotech.com, asamymuthupa@...ron.com,
	snitzer@...hat.com, JBottomley@...allels.com,
	relliott@...rdog.cce.hp.com, sreekanth.reddy@...gotech.com,
	praveen.krishnamoorthy@...gotech.com, agordeev@...hat.com,
	scameron@...rdog.cce.hp.com, tom.leiming@...il.com,
	sbradshaw@...ron.com, hch@....de, m@...rling.me,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH 3/3] mpt3sas, mpt2sas: fix scsi_add_host error handling
	problems in _scsih_probe

On Thu, Jul 17, 2014 at 02:39:30PM -0500, Robert Elliott wrote:
> In _scsih_probe, propagate the return value from scsi_add_host.
> In mpt3sas, avoid calling list_del twice if that returns an
> error, which causes list_del corruption warnings if an error
> is returned.
> 
> Tested with blk-mq and scsi-mq patches to properly cleanup
> from and propagate blk_mq_init_rq_map errors.
> 
> Signed-off-by: Robert Elliott <elliott@...com>

Looks good.  It would be even better if we'd have proper error values
returned from mpt2/3sas_base_attach as well.

Reviewed-by: Christoph Hellwig <hch@....de>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/