From: Chao Yu <chao@kernel.org>
To: Yangtao Li <frank.li@vivo.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: add sanity check for proc_mkdir
Date: Mon, 24 Apr 2023 00:03:21 +0800 [thread overview]
Message-ID: <99c955da-6551-dd63-6587-7f515dd5be32@kernel.org> (raw)
In-Reply-To: <20230406193716.70796-1-frank.li@vivo.com>
On 2023/4/7 3:37, Yangtao Li wrote:
> Return -ENOMEM when proc_mkdir failed.
>
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
> fs/f2fs/sysfs.c | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/fs/f2fs/sysfs.c b/fs/f2fs/sysfs.c
> index 3aad3500a701..dcd497e0920a 100644
> --- a/fs/f2fs/sysfs.c
> +++ b/fs/f2fs/sysfs.c
> @@ -1385,12 +1385,19 @@ int __init f2fs_init_sysfs(void)
>
> ret = kobject_init_and_add(&f2fs_feat, &f2fs_feat_ktype,
> NULL, "features");
> - if (ret) {
> - kobject_put(&f2fs_feat);
> - kset_unregister(&f2fs_kset);
> - } else {
> - f2fs_proc_root = proc_mkdir("fs/f2fs", NULL);
> + if (ret)
> + goto put_kobject;
> +
> + f2fs_proc_root = proc_mkdir("fs/f2fs", NULL);
> + if (!f2fs_proc_root) {
How about removing below check for f2fs_proc_root in f2fs_register_sysfs()?
if (f2fs_proc_root)
sbi->s_proc = proc_mkdir(sb->s_id, f2fs_proc_root);
Thanks,
> + ret = -ENOMEM;
> + goto put_kobject;
> }
> +
> + return 0;
> +put_kobject:
> + kobject_put(&f2fs_feat);
> + kset_unregister(&f2fs_kset);
> return ret;
> }
>
prev parent reply other threads:[~2023-04-23 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 19:37 [PATCH] f2fs: add sanity check for proc_mkdir Yangtao Li
2023-04-07 2:39 ` Bagas Sanjaya
2023-04-23 16:03 ` Chao Yu [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=99c955da-6551-dd63-6587-7f515dd5be32@kernel.org \
--to=chao@kernel.org \
--cc=frank.li@vivo.com \
--cc=jaegeuk@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox