diff for duplicates of <00ef01d1e448$225132a0$66f397e0$@opengridcomputing.com> diff --git a/a/1.txt b/N1/1.txt index 1fbe8a5..ab4490d 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -13,7 +13,7 @@ > 4. safely queue controller deletion (and wait for it > to complete). > -> Signed-off-by: Sagi Grimberg <sagi at grimberg.me> +> Signed-off-by: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org> > --- > drivers/nvme/host/rdma.c | 49 ++++++++++++++++++++++++++---------------------- @@ -98,3 +98,9 @@ Actually, since the queue_work() fires off the workq thread to delete the controller and its resources (on another cpu potentially), and think the flush_work() could end up being a touch-after-free because it accesses *ctrl, no? + + +-- +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 720a1c5..e2a8e5c 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,8 +1,15 @@ "ref\0cover.1468879135.git.swise@opengridcomputing.com\0" "ref\00cb1ccaa920b3ec48dd94ea49fa0f0b7c5520d38.1468879135.git.swise@opengridcomputing.com\0" - "From\0swise@opengridcomputing.com (Steve Wise)\0" - "Subject\0[PATCH 3/3] nvme-rdma: Fix device removal handling\0" + "ref\00cb1ccaa920b3ec48dd94ea49fa0f0b7c5520d38.1468879135.git.swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org\0" + "From\0Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>\0" + "Subject\0RE: [PATCH 3/3] nvme-rdma: Fix device removal handling\0" "Date\0Fri, 22 Jul 2016 13:37:43 -0500\0" + "To\0'Sagi Grimberg' <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>" + " linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\0" + "Cc\0sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org" + mlin-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org + hch-jcswGhMUV9g@public.gmane.org + " linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org\0" "\00:1\0" "b\0" "> Device removal sequence may have crashed because the\n" @@ -20,7 +27,7 @@ "> 4. safely queue controller deletion (and wait for it\n" "> to complete).\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 | 49\n" "++++++++++++++++++++++++++----------------------\n" @@ -104,6 +111,12 @@ "Actually, since the queue_work() fires off the workq thread to delete the\n" "controller and its resources (on another cpu potentially), and think the\n" "flush_work() could end up being a touch-after-free because it accesses *ctrl,\n" - no? + "no?\n" + "\n" + "\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 -16939563a53674fc83d6921c693a6eda8fa87fca07d8a6596fa738f73d908630 +fe6b0d670b0c962d70b7c82d6404494a83c6ac4617152f5f5274e2d48c792596
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.