From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, <linux-btrfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] btrfs: fix a resource leak in btrfs_init_sysfs()
Date: Mon, 21 Nov 2022 11:49:56 +0800 [thread overview]
Message-ID: <d017edb7-e2ab-72f8-aa6b-e6671d18f373@huawei.com> (raw)
In-Reply-To: <c3b20a4b-bb32-27a3-b8a0-2b0b7388a335@gmx.com>
On 2022/11/20 11:29, Qu Wenruo wrote:
>
>
> On 2022/11/20 11:11, Qu Wenruo wrote:
>>
>>
>> On 2022/11/19 14:53, Qu Wenruo wrote:
>>>
>>>
>>> On 2022/11/19 14:43, Zhen Lei wrote:
>>>> When btrfs_debug_feature_attr_group fails to be created,
>>>> btrfs_feature_attr_group is not removed.
>>>>
>>>> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
>>>
>>> Reviewed-by: Qu Wenruo <wqu@suse.com>
>>
>> Wait for a minute, should we call sysfs_unmerge_group() first before calling sysfs_remove_group()?
>>
>> As the sysfs_remove_group() will only remove the btrfs_feature_attr_group, and kset_unregister() will only free btrfs_kset, without removing the added btrfs_static_feature_attr_group.
>>
>> I haven't yet find a function that will remove all children attrs in just one go, or did I miss something?
>
> Oh, indeed I missed something.
>
> The following call chain would properly handle every child of a kobj:
>
> kset_unregister()
> |- kobject_del()
> |- __kobject_del()
> |- sysfs_remove_dir()
> |- kernfs_remove()
> |- __kernfs_remove()
> |- do { kernfs_leftmost_descendant(); } while (pos != kn)
>
> The final do {} while () loop will unlink each child kernel_node and free it.
>
> This means, as long as we call kset_unregister(), we should be able to free every child of it.
OK, thanks.
>
>
> So with or without this patch, the error handling should be fine.
>
> Although personally speaking, I'd prefer a more explicit cleanup (with extra sysfs_unmerge_group() call) as going through the above call chain is not that straightforward.
Yes, with sysfs_unmerge_group(), the code logic is clearer.
>
> Thanks,
> Qu
>
>>
>> Thanks,
>> Qu
>>>
>>> Thanks,
>>> Qu
>>>> ---
>>>> fs/btrfs/sysfs.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/fs/btrfs/sysfs.c b/fs/btrfs/sysfs.c
>>>> index 699b54b3acaae0b..947125f2ceaaf96 100644
>>>> --- a/fs/btrfs/sysfs.c
>>>> +++ b/fs/btrfs/sysfs.c
>>>> @@ -2322,7 +2322,7 @@ int __init btrfs_init_sysfs(void)
>>>> #ifdef CONFIG_BTRFS_DEBUG
>>>> ret = sysfs_create_group(&btrfs_kset->kobj, &btrfs_debug_feature_attr_group);
>>>> if (ret)
>>>> - goto out2;
>>>> + goto out_remove_group;
>>>> #endif
>>>> return 0;
> .
>
--
Regards,
Zhen Lei
prev parent reply other threads:[~2022-11-21 3:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 6:43 [PATCH] btrfs: fix a resource leak in btrfs_init_sysfs() Zhen Lei
2022-11-19 6:53 ` Qu Wenruo
2022-11-20 3:11 ` Qu Wenruo
2022-11-20 3:29 ` Qu Wenruo
2022-11-21 3:49 ` Leizhen (ThunderTown) [this message]
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=d017edb7-e2ab-72f8-aa6b-e6671d18f373@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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;
as well as URLs for NNTP newsgroup(s).