Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Subject: Re: [PATCH] kobject: fix possible memory leak in
 kset_create_and_add()
To:     Greg KH <gregkh@linuxfoundation.org>
CC:     <linux-kernel@vger.kernel.org>, <rafael@kernel.org>
References: <20221017023327.1793893-1-yangyingliang@huawei.com>
 <Y0zfPKAgQSrYZg5o@kroah.com>
From:   Yang Yingliang <yangyingliang@huawei.com>
Message-ID: <9c2e91e1-dd07-8a4b-999c-9a2d26ee5f07@huawei.com>
Date:   Mon, 17 Oct 2022 16:13:03 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <Y0zfPKAgQSrYZg5o@kroah.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Precedence: bulk

Hi,

On 2022/10/17 12:51, Greg KH wrote:
> On Mon, Oct 17, 2022 at 10:33:27AM +0800, Yang Yingliang wrote:
>> If kset_register() fails in kset_create_and_add(), the name allocated
>> in kset_create() will be leaked.
> How is kset_create_and_add() failing?  Is this in a real kernel, or
> created with a fake fault injection?
Inject fault while probing module qemu_fw_cfg, kset_create_and_add() may 
fail.

Thanks,
Yang
>
> thanks,
>
> greg k-h
> .