[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160120102228.GP2742@c203.arch.suse.de>
Date: Wed, 20 Jan 2016 11:22:28 +0100
From: Johannes Thumshirn <jthumshirn@...e.de>
To: Sagi Grimberg <sagig@....mellanox.co.il>
Cc: Wenbo Wang <wenbo.wang@...blaze.com>,
Wenbo Wang <mail_weber_wang@....com>,
"keith.busch@...el.com" <keith.busch@...el.com>,
"axboe@...com" <axboe@...com>,
"Wenwei.Tao" <wenwei.tao@...blaze.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>
Subject: Re: [PATCH] NVMe: init nvme queue before enabling irq
On Wed, Jan 20, 2016 at 11:56:01AM +0200, Sagi Grimberg wrote:
>
> >>If it can cause a kernel panic shouldn't it go through stable then as well?
> >
> >Sorry, not quite understand this comment.
> >The "reset process" is the nvme device reset process (performed by nvme_reset_work()) triggered by device fail condition.
> >During normal boot up, nvmeq door bell is initialized in nvme_alloc_queue() which happens before enabling irq, so there is no error.
> >During nvme device reset process, nvme_alloc_queue() is skipped and the race condition exists.
>
> I think what Johannes meant was that this patch should include a
> "CC: stable@...r.kernel.org" tag.
>
Exactly. This makes work for us distribution people a lot easier (i.e. we do
not have to manually scan all commits and decide if we need to backport a
patch or not)
Thanks
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
--
Johannes Thumshirn Storage
jthumshirn@...e.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
Powered by blists - more mailing lists