mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Joe Lawrence <joe.lawrence@stratus.com>
Cc: Jens Axboe <axboe@kernel.dk>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] block,scsi: fixup blk_get_request dead queue scenarios
Date: Fri, 27 Jun 2014 07:59:59 -0400	[thread overview]
Message-ID: <x49egyaef5s.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1406262319140.16358@jlaw-desktop.mno.stratus.com> (Joe Lawrence's message of "Thu, 26 Jun 2014 23:23:29 -0400")

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

> On Thu, 26 Jun 2014, Jeff Moyer wrote:
>> Thanks, Jens.  Joe, the patches don't apply anymore... would you mind
>> sending an updated set so Jens doesn't have to do the fixups?  I think
>> you also need to convert blk_mq_alloc_request, I didn't see that in your
>> patch.
>
> Hi Jeff,
>
> I have a new set that applies on top of 3.16-rc2... but before posting, I 
> wasn't sure what needs to be converted w/regard to blk_mq_alloc_request.  
> As far as I can tell, the new multi-queue block IO queueing implementation 
> via blk_mq_alloc_request should be safe from this bug as it doesn't 
> include any dead queue checks that introduce early exits.

Hi, Joe,

blk_mq_alloc_request will return NULL if blk_mq_queue_enter() returns
non-zero.

Cheers,
Jeff

      reply	other threads:[~2014-06-27 12:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 19:20 Joe Lawrence
2014-06-04 19:20 ` [PATCH v2 1/2] block,scsi: verify return pointer from blk_get_request Joe Lawrence
2014-06-04 19:36   ` Jeff Moyer
2014-06-04 19:20 ` [PATCH v2 2/2] block,scsi: convert and handle ERR_PTR " Joe Lawrence
2014-06-26 16:08 ` [PATCH v2 0/2] block,scsi: fixup blk_get_request dead queue scenarios Jeff Moyer
2014-06-26 16:11   ` Jens Axboe
2014-06-26 17:20     ` Jeff Moyer
2014-06-27  3:23       ` Joe Lawrence
2014-06-27 11:59         ` Jeff Moyer [this message]

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=x49egyaef5s.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --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

Powered by JetHome