From: Omar Sandoval <osandov@osandov.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] posix_acl: cleanup posix_acl_create()
Date: Tue, 27 Jan 2015 04:52:09 +0000 [thread overview]
Message-ID: <20150127045209.GA1608@mew> (raw)
In-Reply-To: <20150124193124.GA18322@mwanda>
Hi, Dan,
On Sat, Jan 24, 2015 at 10:31:24PM +0300, Dan Carpenter wrote:
> If posix_acl_create() returns an error code then "*acl" and
> "*default_acl" can be uninitialized or point to freed memory. This
> causes problems in some of the callers where it is expected that they
> are NULL on error. For example, ocfs2_reflink() has a bug.
>
> fs/ocfs2/refcounttree.c:4329 ocfs2_reflink()
> error: potentially using uninitialized 'default_acl'.
>
> I have re-written this function and re-arranged things so that they are
> set to NULL at the start and then only set to a valid pointer at the end
> of the function.
>
I'm inclined to blame ocfs2 and not posix_acl_create() here. I'd imagine
that most C programmers' intuition is generally not to trust any return
parameters when the return value is an error. Accordingly, a quick scan
of the tree showed that all of the other users of posix_acl_create() are
doing it correctly and only calling posix_acl_release() when it returns
success.
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/fs/posix_acl.c b/fs/posix_acl.c
> index 0855f77..66d2c13 100644
> --- a/fs/posix_acl.c
> +++ b/fs/posix_acl.c
> @@ -546,50 +546,43 @@ int
> posix_acl_create(struct inode *dir, umode_t *mode,
> struct posix_acl **default_acl, struct posix_acl **acl)
> {
> - struct posix_acl *p;
> + struct posix_acl *p, *clone;
> int ret;
>
> + *acl = NULL;
> + *default_acl = NULL;
> +
> if (S_ISLNK(*mode) || !IS_POSIXACL(dir))
> - goto no_acl;
> + return 0;
>
> p = get_acl(dir, ACL_TYPE_DEFAULT);
> - if (IS_ERR(p)) {
> - if (p = ERR_PTR(-EOPNOTSUPP))
> - goto apply_umask;
> - return PTR_ERR(p);
> + if (!p || p = ERR_PTR(-EOPNOTSUPP)) {
> + *mode &= ~current_umask();
> + return 0;
> }
> + if (IS_ERR(p))
> + return PTR_ERR(p);
>
> - if (!p)
> - goto apply_umask;
> -
> - *acl = posix_acl_clone(p, GFP_NOFS);
> - if (!*acl)
> + clone = posix_acl_clone(p, GFP_NOFS);
> + if (!clone)
> return -ENOMEM;
>
> - ret = posix_acl_create_masq(*acl, mode);
> + ret = posix_acl_create_masq(clone, mode);
> if (ret < 0) {
> - posix_acl_release(*acl);
> + posix_acl_release(clone);
> return -ENOMEM;
> }
>
> - if (ret = 0) {
> - posix_acl_release(*acl);
> - *acl = NULL;
> - }
> + if (ret = 0)
> + posix_acl_release(clone);
> + else
> + *acl = clone;
>
> - if (!S_ISDIR(*mode)) {
> + if (!S_ISDIR(*mode))
> posix_acl_release(p);
> - *default_acl = NULL;
> - } else {
> + else
> *default_acl = p;
> - }
> - return 0;
>
> -apply_umask:
> - *mode &= ~current_umask();
> -no_acl:
> - *default_acl = NULL;
> - *acl = NULL;
> return 0;
> }
> EXPORT_SYMBOL_GPL(posix_acl_create);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Omar
WARNING: multiple messages have this Message-ID (diff)
From: Omar Sandoval <osandov@osandov.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] posix_acl: cleanup posix_acl_create()
Date: Mon, 26 Jan 2015 20:52:09 -0800 [thread overview]
Message-ID: <20150127045209.GA1608@mew> (raw)
In-Reply-To: <20150124193124.GA18322@mwanda>
Hi, Dan,
On Sat, Jan 24, 2015 at 10:31:24PM +0300, Dan Carpenter wrote:
> If posix_acl_create() returns an error code then "*acl" and
> "*default_acl" can be uninitialized or point to freed memory. This
> causes problems in some of the callers where it is expected that they
> are NULL on error. For example, ocfs2_reflink() has a bug.
>
> fs/ocfs2/refcounttree.c:4329 ocfs2_reflink()
> error: potentially using uninitialized 'default_acl'.
>
> I have re-written this function and re-arranged things so that they are
> set to NULL at the start and then only set to a valid pointer at the end
> of the function.
>
I'm inclined to blame ocfs2 and not posix_acl_create() here. I'd imagine
that most C programmers' intuition is generally not to trust any return
parameters when the return value is an error. Accordingly, a quick scan
of the tree showed that all of the other users of posix_acl_create() are
doing it correctly and only calling posix_acl_release() when it returns
success.
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/fs/posix_acl.c b/fs/posix_acl.c
> index 0855f77..66d2c13 100644
> --- a/fs/posix_acl.c
> +++ b/fs/posix_acl.c
> @@ -546,50 +546,43 @@ int
> posix_acl_create(struct inode *dir, umode_t *mode,
> struct posix_acl **default_acl, struct posix_acl **acl)
> {
> - struct posix_acl *p;
> + struct posix_acl *p, *clone;
> int ret;
>
> + *acl = NULL;
> + *default_acl = NULL;
> +
> if (S_ISLNK(*mode) || !IS_POSIXACL(dir))
> - goto no_acl;
> + return 0;
>
> p = get_acl(dir, ACL_TYPE_DEFAULT);
> - if (IS_ERR(p)) {
> - if (p == ERR_PTR(-EOPNOTSUPP))
> - goto apply_umask;
> - return PTR_ERR(p);
> + if (!p || p == ERR_PTR(-EOPNOTSUPP)) {
> + *mode &= ~current_umask();
> + return 0;
> }
> + if (IS_ERR(p))
> + return PTR_ERR(p);
>
> - if (!p)
> - goto apply_umask;
> -
> - *acl = posix_acl_clone(p, GFP_NOFS);
> - if (!*acl)
> + clone = posix_acl_clone(p, GFP_NOFS);
> + if (!clone)
> return -ENOMEM;
>
> - ret = posix_acl_create_masq(*acl, mode);
> + ret = posix_acl_create_masq(clone, mode);
> if (ret < 0) {
> - posix_acl_release(*acl);
> + posix_acl_release(clone);
> return -ENOMEM;
> }
>
> - if (ret == 0) {
> - posix_acl_release(*acl);
> - *acl = NULL;
> - }
> + if (ret == 0)
> + posix_acl_release(clone);
> + else
> + *acl = clone;
>
> - if (!S_ISDIR(*mode)) {
> + if (!S_ISDIR(*mode))
> posix_acl_release(p);
> - *default_acl = NULL;
> - } else {
> + else
> *default_acl = p;
> - }
> - return 0;
>
> -apply_umask:
> - *mode &= ~current_umask();
> -no_acl:
> - *default_acl = NULL;
> - *acl = NULL;
> return 0;
> }
> EXPORT_SYMBOL_GPL(posix_acl_create);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Omar
next prev parent reply other threads:[~2015-01-27 4:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 19:31 [patch] posix_acl: cleanup posix_acl_create() Dan Carpenter
2015-01-24 19:31 ` Dan Carpenter
2015-01-27 4:52 ` Omar Sandoval [this message]
2015-01-27 4:52 ` Omar Sandoval
2015-01-27 6:45 ` Dan Carpenter
2015-01-27 6:45 ` Dan Carpenter
2015-03-05 17:46 ` [patch 1/2] ocfs2: dereferencing freed pointers in ocfs2_reflink() Dan Carpenter
2015-03-05 17:46 ` Dan Carpenter
2015-03-05 17:46 ` [Ocfs2-devel] " Dan Carpenter
2015-03-09 15:02 ` Mark Fasheh
2015-03-09 15:02 ` Mark Fasheh
2015-03-09 15:02 ` [Ocfs2-devel] " Mark Fasheh
2015-03-05 17:47 ` [patch 2/2 v2] posix_acl: make posix_acl_create() safer and cleaner Dan Carpenter
2015-03-05 17:47 ` Dan Carpenter
2015-03-05 17:47 ` [Ocfs2-devel] " Dan Carpenter
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=20150127045209.GA1608@mew \
--to=osandov@osandov.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.