All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
	"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
	linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Hannes Reinecke <hare@suse.com>,
	Damien Le Moal <damien.lemoal@wdc.com>,
	Johannes Thumshirn <jthumshirn@suse.de>,
	stable@vger.kernel.org
Subject: Re: [PATCH] scsi-mq: Always unprepare before requeuing a request
Date: Mon, 07 Aug 2017 13:49:58 -0400	[thread overview]
Message-ID: <yq14ltj9sjd.fsf@oracle.com> (raw)
In-Reply-To: <20170803214014.20332-1-bart.vanassche@wdc.com> (Bart Van Assche's message of "Thu, 3 Aug 2017 14:40:14 -0700")


Bart,

> One of the two scsi-mq functions that requeue a request unprepares a
> request before requeueing (scsi_io_completion()) but the other
> function not (__scsi_queue_insert()). Make sure that a request is
> unprepared before requeuing it.

Applied to 4.13/scsi-fixes. Thanks much!

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2017-08-07 17:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 21:40 [PATCH] scsi-mq: Always unprepare before requeuing a request Bart Van Assche
2017-08-04  8:06 ` Damien Le Moal
2017-08-05 11:36 ` Christoph Hellwig
2017-08-07  7:33 ` Johannes Thumshirn
2017-08-07  7:33   ` Johannes Thumshirn
2017-08-07 17:49 ` Martin K. Petersen [this message]
2017-08-10 10:32   ` Michael Ellerman
2017-08-10 10:32     ` Michael Ellerman
2017-08-10 15:26     ` Bart Van Assche
2017-08-10 15:56       ` Brian King
2017-08-11  1:05       ` Michael Ellerman
2017-08-11 15:37         ` Bart Van Assche
2017-08-11  3:18       ` Michael Ellerman

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=yq14ltj9sjd.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=bart.vanassche@wdc.com \
    --cc=damien.lemoal@wdc.com \
    --cc=hare@suse.com \
    --cc=hch@lst.de \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=jthumshirn@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.