linux-kernel - Re: [PATCH v3 0/2] block,scsi: fixup blk_get

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <x49egw36u55.fsf@segfault.boston.devel.redhat.com>
Date:	Tue, 26 Aug 2014 13:24:54 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Jens Axboe <axboe@...nel.dk>,
	Joe Lawrence <joe.lawrence@...atus.com>
Cc:	<linux-kernel@...r.kernel.org>, Jiri Kosina <jkosina@...e.cz>,
	Boaz Harrosh <bharrosh@...asas.com>
Subject: Re: [PATCH v3 0/2] block,scsi: fixup blk_get_request dead queue scenarios

Joe Lawrence <joe.lawrence@...atus.com> writes:

> v2->v3: rebase to 3.16-rc2, consider return values from the
>         blk_mq_alloc_request leg of the blk_get_request callchain
>         (noted by Jeff), noted in the second patch changelog.
>
> 	blk_mq_queue_enter may return 0 or errno, which
>         blk_mq_alloc_request can propogate out via ERR_PTR.
> 	__blk_mq_alloc_request doesn't include any blk_queue_dying
> 	checks, so I'm assuming that its failures can be attributed
>         to -EWOULDBLOCK under !GFP_WAIT conditions.
>
> v1->v2: incorporate Jeff's feedback in bsg_map_hdr() and Reviewed-by
>         tags.
>
> Joe Lawrence (2):
>   block,scsi: verify return pointer from blk_get_request
>   block,scsi: fixup blk_get_request dead queue scenarios

Jens,

Did this patch set fall through the cracks again?

Cheers,
Jeff
--
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/