From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Fix error handling when creating debugfs root in ocfs2_init()
Date: Thu, 6 Nov 2014 15:37:19 +0800 [thread overview]
Message-ID: <545B252F.7070601@huawei.com> (raw)
In-Reply-To: <1415257654-17607-1-git-send-email-jack@suse.cz>
Looks good to me. Thanks.
Reviewed-by: Joseph Qi <joseph.qi@huawei.com>
On 2014/11/6 15:07, Jan Kara wrote:
> Error handling if creation of root of debugfs in ocfs2_init() fails is
> broken. Although error code is set we fail to exit ocfs2_init() with
> error and thus initialization ends with success. Later when mounting a
> filesystem, ocfs2 debugfs entries end up being created in the root of
> debugfs filesystem which is confusing.
>
> Fix the error handling to bail out.
>
> Coverity-id: 1227009
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> fs/ocfs2/super.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> This replaces patch "ocfs2: Remove pointless assignment in ocfs2_init()".
> Things are safer this way and when debugfs dir creation fails, something is
> really wrong.
>
> diff --git a/fs/ocfs2/super.c b/fs/ocfs2/super.c
> index 93c85bc745e1..8e3ac25efb9f 100644
> --- a/fs/ocfs2/super.c
> +++ b/fs/ocfs2/super.c
> @@ -1622,8 +1622,9 @@ static int __init ocfs2_init(void)
>
> ocfs2_debugfs_root = debugfs_create_dir("ocfs2", NULL);
> if (!ocfs2_debugfs_root) {
> - status = -EFAULT;
> + status = -ENOMEM;
> mlog(ML_ERROR, "Unable to create ocfs2 debugfs root.\n");
> + goto out4;
> }
>
> ocfs2_set_locking_protocol();
>
prev parent reply other threads:[~2014-11-06 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 7:07 [Ocfs2-devel] [PATCH] ocfs2: Fix error handling when creating debugfs root in ocfs2_init() Jan Kara
2014-11-06 7:37 ` Joseph Qi [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=545B252F.7070601@huawei.com \
--to=joseph.qi@huawei.com \
--cc=ocfs2-devel@oss.oracle.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