From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Liuwenyi <qingshenlwy@gmail.com>
Cc: viro@zeniv.linux.org.uk, jmorris@namei.org,
joel.becker@oracle.com, hch@lst.de, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, strongzgy@gmail.com,
onlyflyer@gmail.com
Subject: Re: [PATCHv2 03/12]posix_acl: Add the check items
Date: Mon, 21 Dec 2009 09:39:07 -0600 [thread overview]
Message-ID: <20091221153907.GA30127@us.ibm.com> (raw)
In-Reply-To: <4B2F61D7.5000302@gmail.com>
Quoting Liuwenyi (qingshenlwy@gmail.com):
> move the ACL validation check in to fs/posix_acl.c.
> Including nullpointer check and PTR_ERR check.
>
> ---
> Signed-off-by: Liuwenyi <qingshenlwy@gmail.com>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Cc: James Morris <jmorris@namei.org>
> Cc: Joel Becker <joel.becker@oracle.com>
> Cc: Serge Hallyn <serue@us.ibm.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: linux-ext4@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
>
> ---
> diff --git a/fs/ext2/acl.c b/fs/ext2/acl.c
> index a99e543..480fe88 100644
> --- a/fs/ext2/acl.c
> +++ b/fs/ext2/acl.c
> @@ -403,13 +403,11 @@ ext2_xattr_set_acl(struct dentry *dentry, const
> char *name, const void *value,
>
> if (value) {
> acl = posix_acl_from_xattr(value, size);
> - if (IS_ERR(acl))
> - return PTR_ERR(acl);
> - else if (acl) {
> - error = posix_acl_valid(acl);
> - if (error)
> - goto release_and_out;
> - }
> +
> + error = posix_acl_valid(acl);
> + if (error)
> + goto release_and_out;
Don't you also need to either update posix_acl_release() in your
first patch to handle IS_ERR(acl), or else update the release_and_out:
path in each caller?
> +
> } else
> acl = NULL;
>
>
> --
> Best Regards,
> Liuwenyi
prev parent reply other threads:[~2009-12-21 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 11:53 [PATCHv2 03/12]posix_acl: Add the check items Liuwenyi
2009-12-21 11:53 ` Liuwenyi
2009-12-21 15:39 ` Serge E. Hallyn [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=20091221153907.GA30127@us.ibm.com \
--to=serue@us.ibm.com \
--cc=hch@lst.de \
--cc=jmorris@namei.org \
--cc=joel.becker@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=onlyflyer@gmail.com \
--cc=qingshenlwy@gmail.com \
--cc=strongzgy@gmail.com \
--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.