[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190513135235.GD15318@localhost.localdomain>
Date: Mon, 13 May 2019 07:52:35 -0600
From: Keith Busch <kbusch@...nel.org>
To: Akinobu Mita <akinobu.mita@...il.com>
Cc: "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Johannes Berg <johannes@...solutions.net>,
"Busch, Keith" <keith.busch@...el.com>, Jens Axboe <axboe@...com>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
Minwoo Im <minwoo.im.dev@...il.com>,
"Heitke, Kenneth" <kenneth.heitke@...el.com>
Subject: Re: [PATCH v3 6/7] nvme-pci: trigger device coredump on command
timeout
On Sun, May 12, 2019 at 08:54:16AM -0700, Akinobu Mita wrote:
> @@ -2536,6 +2539,9 @@ static void nvme_reset_work(struct work_struct *work)
> if (result)
> goto out;
>
> + nvme_coredump_logs(dev);
If you change nvme_coredump_logs to return an int, check it here for < 0
and abandon the reset if true.
> + nvme_coredump_complete(dev);
> +
> if (dev->ctrl.oacs & NVME_CTRL_OACS_SEC_SUPP) {
> if (!dev->ctrl.opal_dev)
> dev->ctrl.opal_dev =
Powered by blists - more mailing lists