[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E4551D62-F184-4AE9-9349-2A9C2FC886B4@wdc.com>
Date: Wed, 19 May 2021 04:48:17 +0000
From: Chaitanya Kulkarni <Chaitanya.Kulkarni@....com>
To: Wu Bo <wubo40@...wei.com>
CC: "hch@....de" <hch@....de>, "sagi@...mberg.me" <sagi@...mberg.me>,
"kbusch@...nel.org" <kbusch@...nel.org>,
"amit.engel@...l.com" <amit.engel@...l.com>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linfeilong@...wei.com" <linfeilong@...wei.com>
Subject: Re: [PATCH 2/2] nvme-loop: Fix memory leak in nvme_loop_create_ctrl()
Sent from my iPhone
> On May 18, 2021, at 9:35 PM, Wu Bo <wubo40@...wei.com> wrote:
>
> When creating loop ctrl in nvme_loop_create_ctrl(), if nvme_init_ctrl()
> returns fails, the loop ctrl should be freed before
> jumps to the "out" label.
>
> Fixes: 3a85a5de29ea7 ("nvme-loop: add a NVMe loopback host driver")
Please make sure comit logs lines filled up 72 char and
Commit hash is 12 digit.
See the commit logs in the tree to get the better idea.
Powered by blists - more mailing lists