From: Chao Yu <chao2.yu@samsung.com>
To: liuyiyang@hisense.com
Cc: 'fs-devel' <linux-fsdevel@vger.kernel.org>,
'kernel' <linux-kernel@vger.kernel.org>,
'f2fs' <linux-f2fs-devel@lists.sourceforge.net>,
"'Jaegeuk Kim'" <jaegeuk.kim@samsung.com>,
谭姝 <shu.tan@samsung.com>
Subject: RE: [f2fs-dev] [PATCH 0/2] f2fs: remove debufs dir if debugfs_create_file() failed
Date: Tue, 03 Dec 2013 13:49:05 +0800 [thread overview]
Message-ID: <001001ceefeb$86ebb3b0$94c31b10$@samsung.com> (raw)
Hi Liu,
You're right, we should release it instead of holding the resource
with no use. And here are some comments as following.
BTW, your patch is out of format. You'd better not let remote
terminal or editor to instead tab with blanks in the patch.
Thanks,
Yu
> -----Original Message-----
> From: Younger Liu [mailto:younger.liucn@gmail.com]
> Sent: Monday, December 02, 2013 9:16 PM
> To: Jaegeuk Kim
> Cc: fs-devel; kernel; f2fs
> Subject: [f2fs-dev] [PATCH 0/2] f2fs: remove debufs dir if debugfs_create_file() failed
>
> From: Younger Liu <liuyiyang@hisense.com>
>
> When debugfs_create_file() failed in f2fs_create_root_stats(),
> debugfs_root should be removed.
>
> Signed-off-by: Younger Liu <liuyiyang@hisense.com>
> Cc: Younger Liu <younger.liucn@gmail.com>
> Cc: Jaegeuk Kim <jaegeuk.kim@samsung.com>
> ---
> fs/f2fs/debug.c | 20 +++++++++++++++++---
> 1 file changed, 17 insertions(+), 3 deletions(-)
>
> diff --git a/fs/f2fs/debug.c b/fs/f2fs/debug.c
> index a84b0a8..d27b689 100644
> --- a/fs/f2fs/debug.c
> +++ b/fs/f2fs/debug.c
> @@ -340,10 +340,24 @@ void f2fs_destroy_stats(struct f2fs_sb_info *sbi)
>
> void __init f2fs_create_root_stats(void)
> {
> + struct dentry *file;
> +
> debugfs_root = debugfs_create_dir("f2fs", NULL);
> - if (debugfs_root)
> - debugfs_create_file("status", S_IRUGO, debugfs_root,
> - NULL, &stat_fops);
> + if (!debugfs_root)
> + goto bail;
> +
> + file = debugfs_create_file("status", S_IRUGO,
> + debugfs_root, NULL, &stat_fops);
> + if (!file)
> + goto free_debugfs_dir;
> +
> + return;
> +
> +free_debugfs_dir:
> + debugfs_remove(debugfs_root);
debugfs_root = NULL;
> +
> +bail:
> + return;
> }
>
> void f2fs_destroy_root_stats(void)
You should judge debugfs_root value in f2fs_destroy_root_stats
to decide free or not.
> --
> 1.7.9.5
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2013-12-03 5:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 5:49 Chao Yu [this message]
2013-12-03 11:50 ` [PATCH 0/2] f2fs: remove debufs dir if debugfs_create_file() failed Younger Liu
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='001001ceefeb$86ebb3b0$94c31b10$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyiyang@hisense.com \
--cc=shu.tan@samsung.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).