[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN6PR03MB248142AAC3E0D9851D2A841DA0E40@BN6PR03MB2481.namprd03.prod.outlook.com>
Date: Thu, 18 May 2017 13:29:19 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Christoph Hellwig <hch@...radead.org>,
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>,
Long Li <longli@...rosoft.com>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
Stephen Hemminger <sthemmin@...rosoft.com>
Subject: RE: [PATCH] scsi: zero per-cmd driver data for each MQ I/O
> -----Original Message-----
> From: Christoph Hellwig [mailto:hch@...radead.org]
> Sent: Wednesday, May 17, 2017 11:55 PM
> To: Bart Van Assche <Bart.VanAssche@...disk.com>
> Cc: jejb@...ux.vnet.ibm.com; linux-scsi@...r.kernel.org; linux-
> kernel@...r.kernel.org; Long Li <longli@...rosoft.com>;
> martin.petersen@...cle.com; Stephen Hemminger
> <sthemmin@...rosoft.com>; KY Srinivasan <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.
Thanks Christoph.
K. Y
Powered by blists - more mailing lists