From: Max Gurtovoy <maxg@mellanox.com>
To: linux-nvme@lists.infradead.org, hch@lst.de, kbusch@kernel.org,
sagi@grimberg.me
Cc: Max Gurtovoy <maxg@mellanox.com>,
israelr@mellanox.com, james.smart@broadcom.com,
shlomin@mellanox.com
Subject: [PATCH 0/8] small NVMe cleanups/fixes
Date: Thu, 10 Oct 2019 16:28:12 +0300 [thread overview]
Message-ID: <1570714100-15520-1-git-send-email-maxg@mellanox.com> (raw)
Hi Sagi/Christoph/Keith,
This series include few fast-path and code readability improvements from
IsraelR and also few memleak fixes and new status code introduction from
myself.
This series applies cleanly on top of nvme-5.4 branch, commit 3a8ecc935efab
("nvme: retain split access workaround for capability reads")
Israel Rukshin (4):
nvme: Introduce nvme_is_aen_req function
nvmet: Use bio_io_error instead of duplicating it
nvmet: add unlikely check at nvmet_req_alloc_sgl
nvmet-rdma: add unlikely check at nvmet_rdma_map_sgl_keyed
Max Gurtovoy (4):
nvme: introduce "Command Aborted By host" status code
nvme: move common call to nvme_cleanup_cmd to core layer
nvmet-loop: fix possible leakage during error flow
nvme-tcp: fix possible leakage during error flow
drivers/nvme/host/core.c | 6 +++++-
drivers/nvme/host/fc.c | 3 +--
drivers/nvme/host/multipath.c | 1 +
drivers/nvme/host/nvme.h | 5 +++++
drivers/nvme/host/pci.c | 4 +---
drivers/nvme/host/rdma.c | 16 +++++++---------
drivers/nvme/host/tcp.c | 5 +++--
drivers/nvme/target/core.c | 2 +-
drivers/nvme/target/io-cmd-bdev.c | 8 +++-----
drivers/nvme/target/loop.c | 9 +++++----
drivers/nvme/target/rdma.c | 4 ++--
include/linux/nvme.h | 1 +
12 files changed, 35 insertions(+), 29 deletions(-)
--
1.8.3.1
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2019-10-10 13:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 13:28 Max Gurtovoy [this message]
2019-10-10 13:28 ` [PATCH 1/8] nvme: Introduce nvme_is_aen_req function Max Gurtovoy
2019-10-10 13:51 ` Christoph Hellwig
2019-10-10 13:28 ` [PATCH 2/8] nvmet: use bio_io_error instead of duplicating it Max Gurtovoy
2019-10-10 13:51 ` Christoph Hellwig
2019-10-10 13:28 ` [PATCH 3/8] nvmet: add unlikely check at nvmet_req_alloc_sgl Max Gurtovoy
2019-10-10 13:51 ` Christoph Hellwig
2019-10-10 15:27 ` Max Gurtovoy
2019-10-10 13:28 ` [PATCH 4/8] nvmet-rdma: add unlikely check at nvmet_rdma_map_sgl_keyed Max Gurtovoy
2019-10-10 13:28 ` [PATCH 5/8] nvme: introduce "Command Aborted By host" status code Max Gurtovoy
2019-10-10 13:53 ` Christoph Hellwig
2019-10-10 13:28 ` [PATCH 6/8] nvme: move common call to nvme_cleanup_cmd to core layer Max Gurtovoy
2019-10-10 13:56 ` Christoph Hellwig
2019-10-10 13:28 ` [PATCH 7/8] nvmet-loop: fix possible leakage during error flow Max Gurtovoy
2019-10-10 13:28 ` [PATCH 8/8] nvme-tcp: " Max Gurtovoy
2019-10-10 13:56 ` Christoph Hellwig
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=1570714100-15520-1-git-send-email-maxg@mellanox.com \
--to=maxg@mellanox.com \
--cc=hch@lst.de \
--cc=israelr@mellanox.com \
--cc=james.smart@broadcom.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shlomin@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).