From: jsmart2021@gmail.com (James Smart)
Subject: [PATCH 0/2] nvmet: address controller teardown issues
Date: Thu, 28 Sep 2017 08:35:51 -0700 [thread overview]
Message-ID: <20170928153553.13993-1-jsmart2021@gmail.com> (raw)
Controller deletes were showing a nasty stack trace with
flush_work hanging. Looking at the issue, it became clear the
ref counting for nvmet was allowing the controller to be freed
too early causing use after free errors.
First patch addresses ctrl ref counting
second patch addresses flush_work hang
James Smart (2):
nvmet: fix ctlr ref counting
nvmet: Fix fatal_err_work deadlock
drivers/nvme/target/core.c | 42 +++++++++++++++++++++++++++++----------
drivers/nvme/target/fabrics-cmd.c | 1 +
drivers/nvme/target/nvmet.h | 2 ++
3 files changed, 35 insertions(+), 10 deletions(-)
--
2.13.1
next reply other threads:[~2017-09-28 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 15:35 James Smart [this message]
2017-09-28 15:35 ` [PATCH 1/2] nvmet: fix ctlr ref counting James Smart
2017-09-30 18:00 ` Sagi Grimberg
2017-09-30 19:04 ` James Smart
2017-09-28 15:35 ` [PATCH 2/2] nvmet: Fix fatal_err_work deadlock James Smart
2017-09-30 18:09 ` Sagi Grimberg
2017-09-30 19:33 ` James Smart
2017-10-02 22:45 ` Sagi Grimberg
2017-10-19 8:40 ` Johannes Thumshirn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170928153553.13993-1-jsmart2021@gmail.com \
--to=jsmart2021@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.