[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170518065454.GA25180@infradead.org>
Date: Wed, 17 May 2017 23:54:54 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Bart Van Assche <Bart.VanAssche@...disk.com>
Cc: "jejb@...ux.vnet.ibm.com" <jejb@...ux.vnet.ibm.com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"longli@...rosoft.com" <longli@...rosoft.com>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"sthemmin@...rosoft.com" <sthemmin@...rosoft.com>,
"kys@...rosoft.com" <kys@...rosoft.com>
Subject: Re: [PATCH] scsi: zero per-cmd driver data for each MQ I/O
On Wed, May 17, 2017 at 11:05:18PM +0000, Bart Van Assche wrote:
> Thank you for the feedback. I'm working on a patch series that merges the scsi-sq
> and scsi-mq code paths for command initialization and that should fix the bug you
> encountered.
While that sounds great (I tried it a while ago but gave up due to
priorities) I think we should merge this patch as-is and backport it
to stable for now and rebase your series on top of it.
Powered by blists - more mailing lists