From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCH 12/16] nvmet-tcp: make nvmet_tcp_alloc_queue() a void function
Date: Tue, 8 Aug 2023 18:53:50 +0200 [thread overview]
Message-ID: <20230808165354.123499-13-hare@suse.de> (raw)
In-Reply-To: <20230808165354.123499-1-hare@suse.de>
The return value from nvmet_tcp_alloc_queue() are just used to
figure out if sock_release() need to be called. So this patch
moves sock_release() into nvmet_tcp_alloc_queue() and make it
a void function.
Signed-off-by: Hannes Reinecke <hare@suse.de>
---
drivers/nvme/target/tcp.c | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/drivers/nvme/target/tcp.c b/drivers/nvme/target/tcp.c
index 868aa4de2e4c..019b2598d8d1 100644
--- a/drivers/nvme/target/tcp.c
+++ b/drivers/nvme/target/tcp.c
@@ -1621,7 +1621,7 @@ static int nvmet_tcp_set_queue_sock(struct nvmet_tcp_queue *queue)
return ret;
}
-static int nvmet_tcp_alloc_queue(struct nvmet_tcp_port *port,
+static void nvmet_tcp_alloc_queue(struct nvmet_tcp_port *port,
struct socket *newsock)
{
struct nvmet_tcp_queue *queue;
@@ -1629,7 +1629,7 @@ static int nvmet_tcp_alloc_queue(struct nvmet_tcp_port *port,
queue = kzalloc(sizeof(*queue), GFP_KERNEL);
if (!queue)
- return -ENOMEM;
+ goto out_release;
INIT_WORK(&queue->release_work, nvmet_tcp_release_queue_work);
INIT_WORK(&queue->io_work, nvmet_tcp_io_work);
@@ -1666,7 +1666,7 @@ static int nvmet_tcp_alloc_queue(struct nvmet_tcp_port *port,
if (ret)
goto out_destroy_sq;
- return 0;
+ return;
out_destroy_sq:
mutex_lock(&nvmet_tcp_queue_mutex);
list_del_init(&queue->queue_list);
@@ -1678,7 +1678,9 @@ static int nvmet_tcp_alloc_queue(struct nvmet_tcp_port *port,
ida_free(&nvmet_tcp_queue_ida, queue->idx);
out_free_queue:
kfree(queue);
- return ret;
+out_release:
+ pr_err("failed to allocate queue\n");
+ sock_release(newsock);
}
static void nvmet_tcp_accept_work(struct work_struct *w)
@@ -1695,11 +1697,7 @@ static void nvmet_tcp_accept_work(struct work_struct *w)
pr_warn("failed to accept err=%d\n", ret);
return;
}
- ret = nvmet_tcp_alloc_queue(port, newsock);
- if (ret) {
- pr_err("failed to allocate queue\n");
- sock_release(newsock);
- }
+ nvmet_tcp_alloc_queue(port, newsock);
}
}
--
2.35.3
next prev parent reply other threads:[~2023-08-08 16:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 16:53 [PATCHv6 00/16] nvme: In-kernel TLS support for TCP Hannes Reinecke
2023-08-08 16:53 ` [PATCH 01/16] nvme-keyring: register '.nvme' keyring Hannes Reinecke
2023-08-08 16:53 ` [PATCH 02/16] nvme-keyring: define a 'psk' keytype Hannes Reinecke
2023-08-08 16:53 ` [PATCH 03/16] nvme: add TCP TSAS definitions Hannes Reinecke
2023-08-08 16:53 ` [PATCH 04/16] nvme-tcp: add definitions for TLS cipher suites Hannes Reinecke
2023-08-08 16:53 ` [PATCH 05/16] nvme-keyring: implement nvme_tls_psk_default() Hannes Reinecke
2023-08-08 16:53 ` [PATCH 06/16] security/keys: export key_lookup() Hannes Reinecke
2023-08-10 13:41 ` David Howells
2023-08-08 16:53 ` [PATCH 07/16] nvme-tcp: allocate socket file Hannes Reinecke
2023-08-08 16:53 ` [PATCH 08/16] nvme-tcp: enable TLS handshake upcall Hannes Reinecke
2023-08-09 9:47 ` Sagi Grimberg
2023-08-09 10:00 ` Hannes Reinecke
2023-08-08 16:53 ` [PATCH 09/16] nvme-tcp: control message handling for recvmsg() Hannes Reinecke
2023-08-08 16:53 ` [PATCH 10/16] nvme-fabrics: parse options 'keyring' and 'tls_key' Hannes Reinecke
2023-08-09 9:56 ` Sagi Grimberg
2023-08-09 10:02 ` Hannes Reinecke
2023-08-08 16:53 ` [PATCH 11/16] nvmet: make TCP sectype settable via configfs Hannes Reinecke
2023-08-08 16:53 ` Hannes Reinecke [this message]
2023-08-09 10:26 ` [PATCH 12/16] nvmet-tcp: make nvmet_tcp_alloc_queue() a void function Sagi Grimberg
2023-08-08 16:53 ` [PATCH 13/16] nvmet-tcp: allocate socket file Hannes Reinecke
2023-08-09 10:28 ` Sagi Grimberg
2023-08-08 16:53 ` [PATCH 14/16] nvmet: Allow to change 'TSAS' and 'TREQ' Hannes Reinecke
2023-08-09 10:44 ` Sagi Grimberg
2023-08-09 11:18 ` Hannes Reinecke
2023-08-08 16:53 ` [PATCH 15/16] nvmet-tcp: enable TLS handshake upcall Hannes Reinecke
2023-08-09 10:51 ` Sagi Grimberg
2023-08-09 11:33 ` Hannes Reinecke
2023-08-09 12:51 ` Sagi Grimberg
2023-08-09 12:54 ` Sagi Grimberg
2023-08-09 13:24 ` Hannes Reinecke
2023-08-09 13:22 ` Hannes Reinecke
2023-08-10 7:09 ` Hannes Reinecke
2023-08-10 8:04 ` Sagi Grimberg
2023-08-08 16:53 ` [PATCH 16/16] nvmet-tcp: control messages for recvmsg() Hannes Reinecke
2023-08-09 11:30 ` Sagi Grimberg
2023-08-09 11:35 ` Hannes Reinecke
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=20230808165354.123499-13-hare@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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