From: Jens Axboe <axboe@kernel.dk>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Joe Lawrence <joe.lawrence@stratus.com>,
linux-kernel@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>,
Boaz Harrosh <bharrosh@panasas.com>
Subject: Re: [PATCH v3 0/2] block,scsi: fixup blk_get_request dead queue scenarios
Date: Tue, 26 Aug 2014 15:33:52 -0600 [thread overview]
Message-ID: <53FCFD40.2010903@kernel.dk> (raw)
In-Reply-To: <x49mwar54ca.fsf@segfault.boston.devel.redhat.com>
On 08/26/2014 03:27 PM, Jeff Moyer wrote:
> Jens Axboe <axboe@kernel.dk> writes:
>
>> On 08/26/2014 11:24 AM, Jeff Moyer wrote:
>>> Joe Lawrence <joe.lawrence@stratus.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?
>>
>> Falling through the cracks implies that I meant to apply it and did not,
>> which was not the case.
>
> Sorry, I was mislead by our earlier conversation on this (mail inline
> below).
I changed my mind, it didn't feel fully baked to me.
>> But I think we're at the point now where I'm finally comfortable with
>> applying it. So, Joe, could you ensure that it applies to 3.17-rc2,
>> then I will roll it in to the updates for 3.18.
>
> Joe, you will have one hunk to modify for sure, in scsi_ioctl.c. A
> previous patch added a check for null, but ended up returning the wrong
> value (ENOMEM instead of ENODEV).
I have applied the first one, will look over the second one and hand
apply it. Seems the NULL return was completely removed, so we _should_
be ok on the IS_ERR() conversion, though that sort of thing always
worries me a little bit. A NULL return can quickly show up again, and
then they would all fail.
--
Jens Axboe
next prev parent reply other threads:[~2014-08-26 21:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 19:35 [PATCH v3 0/2] block,scsi: fixup blk_get_request dead queue scenarios Joe Lawrence
2014-07-02 19:35 ` [PATCH v3 1/2] block,scsi: verify return pointer from blk_get_request Joe Lawrence
2014-07-02 19:35 ` [PATCH v3 2/2] block,scsi: fixup blk_get_request dead queue scenarios Joe Lawrence
2014-07-02 20:26 ` [PATCH v3 0/2] " Joe Lawrence
2014-08-26 17:24 ` Jeff Moyer
2014-08-26 21:19 ` Jens Axboe
2014-08-26 21:24 ` Jens Axboe
2014-08-26 21:27 ` Jeff Moyer
2014-08-26 21:33 ` Jens Axboe [this message]
2014-08-26 21:37 ` Jens Axboe
2014-08-26 22:01 ` Jeff Moyer
2014-08-27 14:07 ` Jens Axboe
2014-08-27 15:33 ` Joe Lawrence
2014-08-27 15:50 ` Boaz Harrosh
2014-08-27 16:05 ` Jens Axboe
2014-08-27 14:13 ` Joe Lawrence
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53FCFD40.2010903@kernel.dk \
--to=axboe@kernel.dk \
--cc=bharrosh@panasas.com \
--cc=jkosina@suse.cz \
--cc=jmoyer@redhat.com \
--cc=joe.lawrence@stratus.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox