From: Christoph Hellwig <hch@infradead.org>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: Christoph Hellwig <hch@infradead.org>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org, Mark Fasheh <mfasheh@suse.com>,
Joel Becker <jlbec@evilplan.org>,
reiserfs-devel@vger.kernel.org, xfs@oss.sgi.com,
jfs-discussion@lists.sourceforge.net, cluster-devel@redhat.com,
linux-nfs@vger.kernel.org,
Andreas Gruenbacher <andreas.gruenbacher@linbit.com>
Subject: Re: [PATCH 21/21] hfsplus: remove can_set_xattr
Date: Sun, 22 Dec 2013 11:28:18 -0800 [thread overview]
Message-ID: <20131222192818.GA32565@infradead.org> (raw)
In-Reply-To: <636E01BC-12FD-452B-8B1C-320B6EADAEFD@dubeyko.com>
On Sat, Dec 21, 2013 at 08:07:51PM +0300, Vyacheslav Dubeyko wrote:
> > -static int can_set_xattr(struct inode *inode, const char *name,
> > - const void *value, size_t value_len)
>
> This function works for all handlers. So, I don't think that it makes sense
> to delete it.
It "works" in a minimal sense that it won't crash or actively cause
harm. But it also is useless except for the check that we can abuse
the osx namespace to set an attribute in another namespace, which we
still do in the proper way after my patch.
> > - if (!strncmp(name, XATTR_MAC_OSX_PREFIX, XATTR_MAC_OSX_PREFIX_LEN)) {
> > - /*
> > - * This makes sure that we aren't trying to set an
> > - * attribute in a different namespace by prefixing it
> > - * with "osx."
> > - */
> > - if (is_known_namespace(name + XATTR_MAC_OSX_PREFIX_LEN))
> > - return -EOPNOTSUPP;
>
> I think that this check is important. It forbids such combinations as "osx.system.*" or
> "osx.trusted.*", for example. Because "osx.*" is virtual namespace for xattrs that
> it can be under Mac OS X. If you want to set xattr from "system.*" namespace, for example,
> then you need to use another handler. And such namespace should be without
> addition of "osx." prefix.
Right, and we keep exactly the check, just in a different place.
> The __hfsplus_setxattr() is common method for all handlers. So, removing
> this call means that we don't check validity of namespace. I don't think
> that such modification is a right way.
The generic code already checks for the validity of the namespace for
you. xattr_resolve_name in fs/xattr.c makes sure only attributes for a
namespace that the filesystem registered can be set or modified.
> > @@ -841,10 +761,6 @@ int hfsplus_removexattr(struct dentry *dentry, const char *name)
> > if (!HFSPLUS_SB(inode->i_sb)->attr_tree)
> > return -EOPNOTSUPP;
> >
> > - err = can_set_xattr(inode, name, NULL, 0);
>
> Ditto. Moreover, it is used namely hfsplus_removexattr() and not
> __hfsplus_setxattr() for removing xattrs in hfsplus driver. So, removing
> this check is not good way.
Oh, I just noticed that hfsplus does not use the xattr handlers for
removing, while it does for getting and setting xattrs. That's a really
bad a confusing design, and we'll indeed need to fix that as well.
> > if (len > HFSPLUS_ATTR_MAX_STRLEN)
> > return -EOPNOTSUPP;
> >
> > + if (is_known_namespace(name))
> > + return -EOPNOTSUPP;
>
> If common check in __hfsplus_setxattr() will be on the same place then
> this addition doesn't make sense.
Having both does indeed not make sense, but this is the better place to
have it.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
Cc: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-f2fs-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Mark Fasheh <mfasheh-IBi9RG/b67k@public.gmane.org>,
Joel Becker <jlbec-aKy9MeLSZ9dg9hUCZPvPmw@public.gmane.org>,
reiserfs-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org,
jfs-discussion-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
cluster-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Andreas Gruenbacher
<andreas.gruenbacher-63ez5xqkn6DQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 21/21] hfsplus: remove can_set_xattr
Date: Sun, 22 Dec 2013 11:28:18 -0800 [thread overview]
Message-ID: <20131222192818.GA32565@infradead.org> (raw)
In-Reply-To: <636E01BC-12FD-452B-8B1C-320B6EADAEFD-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
On Sat, Dec 21, 2013 at 08:07:51PM +0300, Vyacheslav Dubeyko wrote:
> > -static int can_set_xattr(struct inode *inode, const char *name,
> > - const void *value, size_t value_len)
>
> This function works for all handlers. So, I don't think that it makes sense
> to delete it.
It "works" in a minimal sense that it won't crash or actively cause
harm. But it also is useless except for the check that we can abuse
the osx namespace to set an attribute in another namespace, which we
still do in the proper way after my patch.
> > - if (!strncmp(name, XATTR_MAC_OSX_PREFIX, XATTR_MAC_OSX_PREFIX_LEN)) {
> > - /*
> > - * This makes sure that we aren't trying to set an
> > - * attribute in a different namespace by prefixing it
> > - * with "osx."
> > - */
> > - if (is_known_namespace(name + XATTR_MAC_OSX_PREFIX_LEN))
> > - return -EOPNOTSUPP;
>
> I think that this check is important. It forbids such combinations as "osx.system.*" or
> "osx.trusted.*", for example. Because "osx.*" is virtual namespace for xattrs that
> it can be under Mac OS X. If you want to set xattr from "system.*" namespace, for example,
> then you need to use another handler. And such namespace should be without
> addition of "osx." prefix.
Right, and we keep exactly the check, just in a different place.
> The __hfsplus_setxattr() is common method for all handlers. So, removing
> this call means that we don't check validity of namespace. I don't think
> that such modification is a right way.
The generic code already checks for the validity of the namespace for
you. xattr_resolve_name in fs/xattr.c makes sure only attributes for a
namespace that the filesystem registered can be set or modified.
> > @@ -841,10 +761,6 @@ int hfsplus_removexattr(struct dentry *dentry, const char *name)
> > if (!HFSPLUS_SB(inode->i_sb)->attr_tree)
> > return -EOPNOTSUPP;
> >
> > - err = can_set_xattr(inode, name, NULL, 0);
>
> Ditto. Moreover, it is used namely hfsplus_removexattr() and not
> __hfsplus_setxattr() for removing xattrs in hfsplus driver. So, removing
> this check is not good way.
Oh, I just noticed that hfsplus does not use the xattr handlers for
removing, while it does for getting and setting xattrs. That's a really
bad a confusing design, and we'll indeed need to fix that as well.
> > if (len > HFSPLUS_ATTR_MAX_STRLEN)
> > return -EOPNOTSUPP;
> >
> > + if (is_known_namespace(name))
> > + return -EOPNOTSUPP;
>
> If common check in __hfsplus_setxattr() will be on the same place then
> this addition doesn't make sense.
Having both does indeed not make sense, but this is the better place to
have it.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: cluster-devel@redhat.com, xfs@oss.sgi.com,
Andreas Gruenbacher <andreas.gruenbacher@linbit.com>,
Mark Fasheh <mfasheh@suse.com>,
reiserfs-devel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@infradead.org>,
linux-mtd@lists.infradead.org, viro@zeniv.linux.org.uk,
jfs-discussion@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-btrfs@vger.kernel.org,
Joel Becker <jlbec@evilplan.org>
Subject: Re: [PATCH 21/21] hfsplus: remove can_set_xattr
Date: Sun, 22 Dec 2013 11:28:18 -0800 [thread overview]
Message-ID: <20131222192818.GA32565@infradead.org> (raw)
In-Reply-To: <636E01BC-12FD-452B-8B1C-320B6EADAEFD@dubeyko.com>
On Sat, Dec 21, 2013 at 08:07:51PM +0300, Vyacheslav Dubeyko wrote:
> > -static int can_set_xattr(struct inode *inode, const char *name,
> > - const void *value, size_t value_len)
>
> This function works for all handlers. So, I don't think that it makes sense
> to delete it.
It "works" in a minimal sense that it won't crash or actively cause
harm. But it also is useless except for the check that we can abuse
the osx namespace to set an attribute in another namespace, which we
still do in the proper way after my patch.
> > - if (!strncmp(name, XATTR_MAC_OSX_PREFIX, XATTR_MAC_OSX_PREFIX_LEN)) {
> > - /*
> > - * This makes sure that we aren't trying to set an
> > - * attribute in a different namespace by prefixing it
> > - * with "osx."
> > - */
> > - if (is_known_namespace(name + XATTR_MAC_OSX_PREFIX_LEN))
> > - return -EOPNOTSUPP;
>
> I think that this check is important. It forbids such combinations as "osx.system.*" or
> "osx.trusted.*", for example. Because "osx.*" is virtual namespace for xattrs that
> it can be under Mac OS X. If you want to set xattr from "system.*" namespace, for example,
> then you need to use another handler. And such namespace should be without
> addition of "osx." prefix.
Right, and we keep exactly the check, just in a different place.
> The __hfsplus_setxattr() is common method for all handlers. So, removing
> this call means that we don't check validity of namespace. I don't think
> that such modification is a right way.
The generic code already checks for the validity of the namespace for
you. xattr_resolve_name in fs/xattr.c makes sure only attributes for a
namespace that the filesystem registered can be set or modified.
> > @@ -841,10 +761,6 @@ int hfsplus_removexattr(struct dentry *dentry, const char *name)
> > if (!HFSPLUS_SB(inode->i_sb)->attr_tree)
> > return -EOPNOTSUPP;
> >
> > - err = can_set_xattr(inode, name, NULL, 0);
>
> Ditto. Moreover, it is used namely hfsplus_removexattr() and not
> __hfsplus_setxattr() for removing xattrs in hfsplus driver. So, removing
> this check is not good way.
Oh, I just noticed that hfsplus does not use the xattr handlers for
removing, while it does for getting and setting xattrs. That's a really
bad a confusing design, and we'll indeed need to fix that as well.
> > if (len > HFSPLUS_ATTR_MAX_STRLEN)
> > return -EOPNOTSUPP;
> >
> > + if (is_known_namespace(name))
> > + return -EOPNOTSUPP;
>
> If common check in __hfsplus_setxattr() will be on the same place then
> this addition doesn't make sense.
Having both does indeed not make sense, but this is the better place to
have it.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: cluster-devel@redhat.com, xfs@oss.sgi.com,
Andreas Gruenbacher <andreas.gruenbacher@linbit.com>,
Mark Fasheh <mfasheh@suse.com>,
reiserfs-devel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@infradead.org>,
linux-mtd@lists.infradead.org, viro@zeniv.linux.org.uk,
jfs-discussion@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-btrfs@vger.kernel.org,
Joel Becker <jlbec@evilplan.org>
Subject: Re: [PATCH 21/21] hfsplus: remove can_set_xattr
Date: Sun, 22 Dec 2013 11:28:18 -0800 [thread overview]
Message-ID: <20131222192818.GA32565@infradead.org> (raw)
In-Reply-To: <636E01BC-12FD-452B-8B1C-320B6EADAEFD@dubeyko.com>
On Sat, Dec 21, 2013 at 08:07:51PM +0300, Vyacheslav Dubeyko wrote:
> > -static int can_set_xattr(struct inode *inode, const char *name,
> > - const void *value, size_t value_len)
>
> This function works for all handlers. So, I don't think that it makes sense
> to delete it.
It "works" in a minimal sense that it won't crash or actively cause
harm. But it also is useless except for the check that we can abuse
the osx namespace to set an attribute in another namespace, which we
still do in the proper way after my patch.
> > - if (!strncmp(name, XATTR_MAC_OSX_PREFIX, XATTR_MAC_OSX_PREFIX_LEN)) {
> > - /*
> > - * This makes sure that we aren't trying to set an
> > - * attribute in a different namespace by prefixing it
> > - * with "osx."
> > - */
> > - if (is_known_namespace(name + XATTR_MAC_OSX_PREFIX_LEN))
> > - return -EOPNOTSUPP;
>
> I think that this check is important. It forbids such combinations as "osx.system.*" or
> "osx.trusted.*", for example. Because "osx.*" is virtual namespace for xattrs that
> it can be under Mac OS X. If you want to set xattr from "system.*" namespace, for example,
> then you need to use another handler. And such namespace should be without
> addition of "osx." prefix.
Right, and we keep exactly the check, just in a different place.
> The __hfsplus_setxattr() is common method for all handlers. So, removing
> this call means that we don't check validity of namespace. I don't think
> that such modification is a right way.
The generic code already checks for the validity of the namespace for
you. xattr_resolve_name in fs/xattr.c makes sure only attributes for a
namespace that the filesystem registered can be set or modified.
> > @@ -841,10 +761,6 @@ int hfsplus_removexattr(struct dentry *dentry, const char *name)
> > if (!HFSPLUS_SB(inode->i_sb)->attr_tree)
> > return -EOPNOTSUPP;
> >
> > - err = can_set_xattr(inode, name, NULL, 0);
>
> Ditto. Moreover, it is used namely hfsplus_removexattr() and not
> __hfsplus_setxattr() for removing xattrs in hfsplus driver. So, removing
> this check is not good way.
Oh, I just noticed that hfsplus does not use the xattr handlers for
removing, while it does for getting and setting xattrs. That's a really
bad a confusing design, and we'll indeed need to fix that as well.
> > if (len > HFSPLUS_ATTR_MAX_STRLEN)
> > return -EOPNOTSUPP;
> >
> > + if (is_known_namespace(name))
> > + return -EOPNOTSUPP;
>
> If common check in __hfsplus_setxattr() will be on the same place then
> this addition doesn't make sense.
Having both does indeed not make sense, but this is the better place to
have it.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 21/21] hfsplus: remove can_set_xattr
Date: Sun, 22 Dec 2013 11:28:18 -0800 [thread overview]
Message-ID: <20131222192818.GA32565@infradead.org> (raw)
In-Reply-To: <636E01BC-12FD-452B-8B1C-320B6EADAEFD@dubeyko.com>
On Sat, Dec 21, 2013 at 08:07:51PM +0300, Vyacheslav Dubeyko wrote:
> > -static int can_set_xattr(struct inode *inode, const char *name,
> > - const void *value, size_t value_len)
>
> This function works for all handlers. So, I don't think that it makes sense
> to delete it.
It "works" in a minimal sense that it won't crash or actively cause
harm. But it also is useless except for the check that we can abuse
the osx namespace to set an attribute in another namespace, which we
still do in the proper way after my patch.
> > - if (!strncmp(name, XATTR_MAC_OSX_PREFIX, XATTR_MAC_OSX_PREFIX_LEN)) {
> > - /*
> > - * This makes sure that we aren't trying to set an
> > - * attribute in a different namespace by prefixing it
> > - * with "osx."
> > - */
> > - if (is_known_namespace(name + XATTR_MAC_OSX_PREFIX_LEN))
> > - return -EOPNOTSUPP;
>
> I think that this check is important. It forbids such combinations as "osx.system.*" or
> "osx.trusted.*", for example. Because "osx.*" is virtual namespace for xattrs that
> it can be under Mac OS X. If you want to set xattr from "system.*" namespace, for example,
> then you need to use another handler. And such namespace should be without
> addition of "osx." prefix.
Right, and we keep exactly the check, just in a different place.
> The __hfsplus_setxattr() is common method for all handlers. So, removing
> this call means that we don't check validity of namespace. I don't think
> that such modification is a right way.
The generic code already checks for the validity of the namespace for
you. xattr_resolve_name in fs/xattr.c makes sure only attributes for a
namespace that the filesystem registered can be set or modified.
> > @@ -841,10 +761,6 @@ int hfsplus_removexattr(struct dentry *dentry, const char *name)
> > if (!HFSPLUS_SB(inode->i_sb)->attr_tree)
> > return -EOPNOTSUPP;
> >
> > - err = can_set_xattr(inode, name, NULL, 0);
>
> Ditto. Moreover, it is used namely hfsplus_removexattr() and not
> __hfsplus_setxattr() for removing xattrs in hfsplus driver. So, removing
> this check is not good way.
Oh, I just noticed that hfsplus does not use the xattr handlers for
removing, while it does for getting and setting xattrs. That's a really
bad a confusing design, and we'll indeed need to fix that as well.
> > if (len > HFSPLUS_ATTR_MAX_STRLEN)
> > return -EOPNOTSUPP;
> >
> > + if (is_known_namespace(name))
> > + return -EOPNOTSUPP;
>
> If common check in __hfsplus_setxattr() will be on the same place then
> this addition doesn't make sense.
Having both does indeed not make sense, but this is the better place to
have it.
next prev parent reply other threads:[~2013-12-22 19:28 UTC|newest]
Thread overview: 146+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 13:16 [PATCH 00/21] Consolidate Posix ACL implementation V3 Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 01/21] reiserfs: prefix ACL symbols with reiserfs_ Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 02/21] fs: merge xattr_acl.c into posix_acl.c Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 03/21] fs: add get_acl helper Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 04/21] fs: add a set_acl inode operation Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 05/21] fs: add generic xattr_acl handlers Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 06/21] fs: make posix_acl_chmod more useful Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 07/21] fs: make posix_acl_create " Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 08/21] btrfs: use generic posix ACL infrastructure Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 09/21] ext2/3/4: " Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 10/21] f2fs: " Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 11/21] hfsplus: " Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 12/21] jffs2: " Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 13/21] ocfs2: " Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 14/21] reiserfs: " Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 15/21] xfs: " Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 16/21] jfs: " Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 17/21] gfs2: " Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 18/21] nfs: use generic posix ACL infrastructure for v3 Posix ACLs Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 19/21] fs: remove generic_acl Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 20/21] nfsd: use get_acl and ->set_acl Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` [PATCH 21/21] hfsplus: remove can_set_xattr Christoph Hellwig
2013-12-20 13:16 ` [Cluster-devel] " Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-20 13:16 ` Christoph Hellwig
2013-12-21 17:07 ` Vyacheslav Dubeyko
2013-12-21 17:07 ` [Cluster-devel] " Vyacheslav Dubeyko
2013-12-21 17:07 ` Vyacheslav Dubeyko
2013-12-21 17:07 ` Vyacheslav Dubeyko
2013-12-22 19:28 ` Christoph Hellwig [this message]
2013-12-22 19:28 ` [Cluster-devel] " Christoph Hellwig
2013-12-22 19:28 ` Christoph Hellwig
2013-12-22 19:28 ` Christoph Hellwig
2013-12-22 19:28 ` Christoph Hellwig
2013-12-23 6:40 ` Vyacheslav Dubeyko
2013-12-23 6:40 ` [Cluster-devel] " Vyacheslav Dubeyko
2013-12-23 6:40 ` Vyacheslav Dubeyko
2013-12-23 6:40 ` Vyacheslav Dubeyko
2013-12-23 14:37 ` Christoph Hellwig
2013-12-23 14:37 ` [Cluster-devel] " Christoph Hellwig
2013-12-23 14:37 ` Christoph Hellwig
2013-12-23 14:37 ` Christoph Hellwig
2013-12-24 6:41 ` Vyacheslav Dubeyko
2013-12-24 6:41 ` [Cluster-devel] " Vyacheslav Dubeyko
2013-12-24 6:41 ` Vyacheslav Dubeyko
2013-12-24 6:41 ` Vyacheslav Dubeyko
2013-12-26 9:48 ` Christoph Hellwig
2013-12-26 10:15 ` Vyacheslav Dubeyko
2013-12-26 10:45 ` Christoph Hellwig
2013-12-26 10:59 ` Vyacheslav Dubeyko
2013-12-23 16:57 ` [PATCH 00/21] Consolidate Posix ACL implementation V3 Chris Mason
2013-12-23 16:57 ` [Cluster-devel] " Chris Mason
2013-12-23 16:57 ` Chris Mason
2013-12-23 16:57 ` Chris Mason
2013-12-23 16:57 ` Chris Mason
2013-12-23 17:01 ` hch
2013-12-23 17:01 ` [Cluster-devel] " hch
2013-12-23 17:01 ` hch
2013-12-23 17:01 ` hch
2013-12-23 17:01 ` hch
2014-01-07 15:53 ` Christoph Hellwig
2014-01-07 15:53 ` [Cluster-devel] " Christoph Hellwig
2014-01-07 15:53 ` Christoph Hellwig
2014-01-07 15:53 ` Christoph Hellwig
2014-01-07 15:53 ` Christoph Hellwig
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=20131222192818.GA32565@infradead.org \
--to=hch@infradead.org \
--cc=andreas.gruenbacher@linbit.com \
--cc=cluster-devel@redhat.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=jlbec@evilplan.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=viro@zeniv.linux.org.uk \
--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 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.