From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Yangtao Li <frank.li@vivo.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: remove bulk remove_proc_entry() and unnecessary kobject_del()
Date: Thu, 13 Apr 2023 08:54:52 -0700 [thread overview]
Message-ID: <ZDglzIoEp3dH3eOS@google.com> (raw)
In-Reply-To: <2e41d6e0-13bb-fa5d-00aa-75865b8e7c34@kernel.org>
On 04/13, Chao Yu wrote:
> On 2023/4/7 3:16, Yangtao Li wrote:
> > Convert to use remove_proc_subtree() and kill kobject_del() directly.
> > kobject_put() actually covers kobject removal automatically, which is
> > single stage removal.
> >
> > Signed-off-by: Yangtao Li <frank.li@vivo.com>
> > ---
> > fs/f2fs/sysfs.c | 15 ++-------------
> > 1 file changed, 2 insertions(+), 13 deletions(-)
> >
> > diff --git a/fs/f2fs/sysfs.c b/fs/f2fs/sysfs.c
> > index dfbd17802549..3aad3500a701 100644
> > --- a/fs/f2fs/sysfs.c
> > +++ b/fs/f2fs/sysfs.c
> > @@ -1461,25 +1461,14 @@ int f2fs_register_sysfs(struct f2fs_sb_info *sbi)
> > void f2fs_unregister_sysfs(struct f2fs_sb_info *sbi)
> > {
> > - if (sbi->s_proc) {
> > -#ifdef CONFIG_F2FS_IOSTAT
> > - remove_proc_entry("iostat_info", sbi->s_proc);
> > -#endif
> > - remove_proc_entry("segment_info", sbi->s_proc);
> > - remove_proc_entry("segment_bits", sbi->s_proc);
> > - remove_proc_entry("victim_bits", sbi->s_proc);
> > - remove_proc_entry("discard_plist_info", sbi->s_proc);
> > - remove_proc_entry(sbi->sb->s_id, f2fs_proc_root);
> > - }
> > + if (sbi->s_proc)
> > + remove_proc_subtree(sbi->sb->s_id, f2fs_proc_root);
> > - kobject_del(&sbi->s_stat_kobj);
>
> - f2fs_register_sysfs
> - kobject_init_and_add(&sbi->s_stat_kobj, ..)
>
> /**
> * kobject_init_and_add() - Initialize a kobject structure and add it to
> * the kobject hierarchy.
> ...
> *
> * This function combines the call to kobject_init() and kobject_add().
> ...
> */
>
> /**
> * kobject_del() - Unlink kobject from hierarchy.
> * @kobj: object.
> *
> * This is the function that should be called to delete an object
> * successfully added via kobject_add().
> */
>
> Am I missing something?
kobject_put -> kobject_cleanup was supposed to do it?
>
> Thanks,
>
> > kobject_put(&sbi->s_stat_kobj);
> > wait_for_completion(&sbi->s_stat_kobj_unregister);
> > - kobject_del(&sbi->s_feature_list_kobj);
> > kobject_put(&sbi->s_feature_list_kobj);
> > wait_for_completion(&sbi->s_feature_list_kobj_unregister);
> > - kobject_del(&sbi->s_kobj);
> > kobject_put(&sbi->s_kobj);
> > wait_for_completion(&sbi->s_kobj_unregister);
> > }
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: Yangtao Li <frank.li@vivo.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: remove bulk remove_proc_entry() and unnecessary kobject_del()
Date: Thu, 13 Apr 2023 08:54:52 -0700 [thread overview]
Message-ID: <ZDglzIoEp3dH3eOS@google.com> (raw)
In-Reply-To: <2e41d6e0-13bb-fa5d-00aa-75865b8e7c34@kernel.org>
On 04/13, Chao Yu wrote:
> On 2023/4/7 3:16, Yangtao Li wrote:
> > Convert to use remove_proc_subtree() and kill kobject_del() directly.
> > kobject_put() actually covers kobject removal automatically, which is
> > single stage removal.
> >
> > Signed-off-by: Yangtao Li <frank.li@vivo.com>
> > ---
> > fs/f2fs/sysfs.c | 15 ++-------------
> > 1 file changed, 2 insertions(+), 13 deletions(-)
> >
> > diff --git a/fs/f2fs/sysfs.c b/fs/f2fs/sysfs.c
> > index dfbd17802549..3aad3500a701 100644
> > --- a/fs/f2fs/sysfs.c
> > +++ b/fs/f2fs/sysfs.c
> > @@ -1461,25 +1461,14 @@ int f2fs_register_sysfs(struct f2fs_sb_info *sbi)
> > void f2fs_unregister_sysfs(struct f2fs_sb_info *sbi)
> > {
> > - if (sbi->s_proc) {
> > -#ifdef CONFIG_F2FS_IOSTAT
> > - remove_proc_entry("iostat_info", sbi->s_proc);
> > -#endif
> > - remove_proc_entry("segment_info", sbi->s_proc);
> > - remove_proc_entry("segment_bits", sbi->s_proc);
> > - remove_proc_entry("victim_bits", sbi->s_proc);
> > - remove_proc_entry("discard_plist_info", sbi->s_proc);
> > - remove_proc_entry(sbi->sb->s_id, f2fs_proc_root);
> > - }
> > + if (sbi->s_proc)
> > + remove_proc_subtree(sbi->sb->s_id, f2fs_proc_root);
> > - kobject_del(&sbi->s_stat_kobj);
>
> - f2fs_register_sysfs
> - kobject_init_and_add(&sbi->s_stat_kobj, ..)
>
> /**
> * kobject_init_and_add() - Initialize a kobject structure and add it to
> * the kobject hierarchy.
> ...
> *
> * This function combines the call to kobject_init() and kobject_add().
> ...
> */
>
> /**
> * kobject_del() - Unlink kobject from hierarchy.
> * @kobj: object.
> *
> * This is the function that should be called to delete an object
> * successfully added via kobject_add().
> */
>
> Am I missing something?
kobject_put -> kobject_cleanup was supposed to do it?
>
> Thanks,
>
> > kobject_put(&sbi->s_stat_kobj);
> > wait_for_completion(&sbi->s_stat_kobj_unregister);
> > - kobject_del(&sbi->s_feature_list_kobj);
> > kobject_put(&sbi->s_feature_list_kobj);
> > wait_for_completion(&sbi->s_feature_list_kobj_unregister);
> > - kobject_del(&sbi->s_kobj);
> > kobject_put(&sbi->s_kobj);
> > wait_for_completion(&sbi->s_kobj_unregister);
> > }
next prev parent reply other threads:[~2023-04-13 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 19:16 [f2fs-dev] [PATCH] f2fs: remove bulk remove_proc_entry() and unnecessary kobject_del() Yangtao Li via Linux-f2fs-devel
2023-04-06 19:16 ` Yangtao Li
2023-04-13 15:18 ` [f2fs-dev] " Chao Yu
2023-04-13 15:18 ` Chao Yu
2023-04-13 15:54 ` Jaegeuk Kim [this message]
2023-04-13 15:54 ` Jaegeuk Kim
2023-04-16 15:02 ` [f2fs-dev] " Chao Yu
2023-04-16 15:02 ` Chao Yu
2023-04-17 21:50 ` [f2fs-dev] " patchwork-bot+f2fs
2023-04-17 21:50 ` patchwork-bot+f2fs
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=ZDglzIoEp3dH3eOS@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=frank.li@vivo.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.