diff for duplicates of <20160801110446.GD16141@lst.de> diff --git a/a/1.txt b/N1/1.txt index bbddb16..8befc9c 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -On Fri, Jul 29, 2016@10:57:20PM +0300, Sagi Grimberg wrote: +On Fri, Jul 29, 2016 at 10:57:20PM +0300, Sagi Grimberg wrote: > Relying on ctrl state in nvme_rdma_shutdown_ctrl is wrong because > it will never be NVME_CTRL_LIVE (delete_ctrl or reset_ctrl invoked it). > @@ -6,7 +6,7 @@ On Fri, Jul 29, 2016@10:57:20PM +0300, Sagi Grimberg wrote: > because we can never see a copmeting thread trying to destroy the admin > queue (reset or delete controller). > -> Signed-off-by: Sagi Grimberg <sagi at grimberg.me> +> Signed-off-by: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org> > --- > drivers/nvme/host/rdma.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) @@ -28,3 +28,7 @@ On Fri, Jul 29, 2016@10:57:20PM +0300, Sagi Grimberg wrote: Maybe the right way to handle this is to unconditionally call nvme_shutdown_ctrl and make sure we return an early error on the register write? +-- +To unsubscribe from this list: send the line "unsubscribe linux-rdma" in +the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 26b15f1..a55cb94 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,11 +1,19 @@ "ref\01469822242-3477-1-git-send-email-sagi@grimberg.me\0" "ref\01469822242-3477-4-git-send-email-sagi@grimberg.me\0" - "From\0hch@lst.de (Christoph Hellwig)\0" - "Subject\0[PATCH 3/5] nvme-rdma: Make sure to shutdown the controller if we can\0" + "ref\01469822242-3477-4-git-send-email-sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org\0" + "From\0Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>\0" + "Subject\0Re: [PATCH 3/5] nvme-rdma: Make sure to shutdown the controller if we can\0" "Date\0Mon, 1 Aug 2016 13:04:46 +0200\0" + "To\0Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>\0" + "Cc\0linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" + linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org> + Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org> + Jay Freyensee <james_p_freyensee-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> + " Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>\0" "\00:1\0" "b\0" - "On Fri, Jul 29, 2016@10:57:20PM +0300, Sagi Grimberg wrote:\n" + "On Fri, Jul 29, 2016 at 10:57:20PM +0300, Sagi Grimberg wrote:\n" "> Relying on ctrl state in nvme_rdma_shutdown_ctrl is wrong because\n" "> it will never be NVME_CTRL_LIVE (delete_ctrl or reset_ctrl invoked it).\n" "> \n" @@ -13,7 +21,7 @@ "> because we can never see a copmeting thread trying to destroy the admin\n" "> queue (reset or delete controller).\n" "> \n" - "> Signed-off-by: Sagi Grimberg <sagi at grimberg.me>\n" + "> Signed-off-by: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>\n" "> ---\n" "> drivers/nvme/host/rdma.c | 2 +-\n" "> 1 file changed, 1 insertion(+), 1 deletion(-)\n" @@ -34,6 +42,10 @@ "\n" "Maybe the right way to handle this is to unconditionally call\n" "nvme_shutdown_ctrl and make sure we return an early error\n" - on the register write? + "on the register write?\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-rdma\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -47c368e9b71a524e7101fffd3052ba42400ae33da774ef0ae7d06ff15c36a30f +12872ab9fc14c95c640bc8aa344756834d6254e6ea367feeebe8193784ddab52
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.