From: liu weni <qingshenlwy@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: chris.mason@oracle.com, viro@zeniv.linux.org.uk,
joel.becker@oracle.com, cjb@laptop.org, jmorris@namei.org,
serue@us.ibm.com, akpm@linux-foundation.org, adilger@sun.com,
jack@suse.cz, tytso@mit.edu, dwmw2@infradead.xn.org.cpa,
swhiteho@redhat.com, bfields@fieldses.org, neilb@suse.de,
ffilzlnx@us.ibm.com, bharrosh@panasas.com, mfasheh@suse.com,
tiger.yang@oracle.com, jeffm@suse.com, aelder@sgi.com,
sandeen@sandeen.net, xfs-masters@oss.sgi.com, xfs@oss.sgi.com,
reiserfs-devel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
linux-nfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, cluster-devel@redhat.com,
linux-mtd@lists.infradead.org, strongzgy@gmail.com,
onlyflyer@gmail.com
Subject: Re: [PATCHv2 00/12]posix_acl: Add the check items
Date: Mon, 21 Dec 2009 22:15:26 +0800 [thread overview]
Message-ID: <b3657a100912210615q1d55c334g73667e1c3a97ce05@mail.gmail.com> (raw)
In-Reply-To: <20091221123654.GA9201@lst.de>
Thanks for your suggestion.
In my opinion the null point is a incorrect state for the acl, then I
return -EINVAL.
I will check this state transition in XFS.
2009/12/21 Christoph Hellwig <hch@lst.de>:
> I like taking these checks into posix_acl_valid, but I think the patch
> submission needs a bit more work.
>
> All the patches are extremly whitespace mangled. And I don't think
> splitting them up makes a whole lot of sense, when we do API changes
> like this we usually fix up all callers. So please try to fix your
> mailer, merged them all into one, and maybe also chose a more
> descriptive subject line, e.g.
>
> Subject: take checks for NULL and error pointers into posix_acl_valid()
>
>
> And btw, at least the XFS change seems incorrect - previously we
> returned NULL acl pointer and this patch changes it to -EINVAL.
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-12-21 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B2F6153.8010609@gmail.com>
2009-12-21 12:37 ` [PATCHv2 00/12]posix_acl: Add the check items Christoph Hellwig
2009-12-21 14:15 ` liu weni [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=b3657a100912210615q1d55c334g73667e1c3a97ce05@mail.gmail.com \
--to=qingshenlwy@gmail.com \
--cc=adilger@sun.com \
--cc=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=bharrosh@panasas.com \
--cc=chris.mason@oracle.com \
--cc=cjb@laptop.org \
--cc=cluster-devel@redhat.com \
--cc=dwmw2@infradead.xn.org.cpa \
--cc=ffilzlnx@us.ibm.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jeffm@suse.com \
--cc=jmorris@namei.org \
--cc=joel.becker@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=neilb@suse.de \
--cc=ocfs2-devel@oss.oracle.com \
--cc=onlyflyer@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=serue@us.ibm.com \
--cc=strongzgy@gmail.com \
--cc=swhiteho@redhat.com \
--cc=tiger.yang@oracle.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.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).