Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Jens Axboe <axboe@kernel.dk>
To:     Hannes Reinecke <hare@suse.de>, linux-kernel@vger.kernel.org,
        Miaoqian Lin <linmq006@gmail.com>, linux-block@vger.kernel.org,
        Damien Le Moal <damien.lemoal@wdc.com>,
        "Martin K. Petersen" <martin.petersen@oracle.com>,
        Keith Busch <kbusch@kernel.org>
In-Reply-To: <20220120101025.22411-1-linmq006@gmail.com>
References: <20220120101025.22411-1-linmq006@gmail.com>
Subject: Re: [PATCH] block: fix memory leak in disk_register_independent_access_ranges
Message-Id: <164278728249.232198.7158002983506256334.b4-ty@kernel.dk>
Date:   Fri, 21 Jan 2022 10:48:02 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 20 Jan 2022 10:10:25 +0000, Miaoqian Lin wrote:
> kobject_init_and_add() takes reference even when it fails.
> According to the doc of kobject_init_and_add()
> 
>    If this function returns an error, kobject_put() must be called to
>    properly clean up the memory associated with the object.
> 
> Fix this issue by adding kobject_put().
> Callback function blk_ia_ranges_sysfs_release() in kobject_put()
> can handle the pointer "iars" properly.
> 
> [...]

Applied, thanks!

[1/1] block: fix memory leak in disk_register_independent_access_ranges
      commit: c321e650a45c4228cce1107680ac74e06f014906

Best regards,
-- 
Jens Axboe