[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231030132954.GD21741@lst.de>
Date: Mon, 30 Oct 2023 14:29:54 +0100
From: Christoph Hellwig <hch@....de>
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
Hannes Reinecke <hare@...e.de>, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org, linux-nvme@...ts.infradead.org
Subject: Re: [PATCH] nvme-tcp: Fix a memory leak
On Sun, Oct 29, 2023 at 10:22:57PM +0100, Christophe JAILLET wrote:
> if (ctype != TLS_RECORD_TYPE_DATA) {
> pr_err("queue %d: unhandled TLS record %d\n",
> nvme_tcp_queue_id(queue), ctype);
> - return -ENOTCONN;
> + ret = -ENOTCONN;
> + goto free_icresp;
> }
> }
> ret = -EINVAL;
I'd slightly prefer the code to be consistent how it assigns to err,
and use the style where it is assigned in the main path as with the
-EINVAL for the next checks.
Except for that this looks good:
Reviewed-by: Christoph Hellwig <hch@....de>
Powered by blists - more mailing lists