diff options
| author | Eric Sandeen <sandeen@sandeen.net> | 2008-04-17 16:50:22 +1000 |
|---|---|---|
| committer | Lachlan McIlroy <lachlan@redback.melbourne.sgi.com> | 2008-04-18 12:04:19 +1000 |
| commit | f7d3c34788696f5ba9ac9fa414ad80e2a91d4b2e (patch) | |
| tree | 0e8d743bdb6344a20b61a8daeb23bf3b508ff573 /fs/xfs/xfs_attr.c | |
| parent | 6d1337b29bf09a97682d39db36ac2d0dfc6659c0 (diff) | |
| download | kernel_samsung_tuna-f7d3c34788696f5ba9ac9fa414ad80e2a91d4b2e.zip kernel_samsung_tuna-f7d3c34788696f5ba9ac9fa414ad80e2a91d4b2e.tar.gz kernel_samsung_tuna-f7d3c34788696f5ba9ac9fa414ad80e2a91d4b2e.tar.bz2 | |
[XFS] Remove CONFIG_XFS_SECURITY.
There is no point to the CONFIG_XFS_SECURITY option; it disables the
ability to set security attributes at runtime, but it does not actually
slim down or remove any code for runtime. Just remove it and always allow
security attributes to be set.
SGI-PV: 980310
SGI-Modid: xfs-linux-melb:xfs-kern:30877a
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Signed-off-by: Tim Shimmin <tes@sgi.com>
Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
Diffstat (limited to 'fs/xfs/xfs_attr.c')
| -rw-r--r-- | fs/xfs/xfs_attr.c | 10 |
1 files changed, 1 insertions, 9 deletions
diff --git a/fs/xfs/xfs_attr.c b/fs/xfs/xfs_attr.c index e58f321..36d781e 100644 --- a/fs/xfs/xfs_attr.c +++ b/fs/xfs/xfs_attr.c @@ -2647,14 +2647,6 @@ attr_trusted_capable( } STATIC int -attr_secure_capable( - bhv_vnode_t *vp, - cred_t *cred) -{ - return -ENOSECURITY; -} - -STATIC int attr_system_set( bhv_vnode_t *vp, char *name, void *data, size_t size, int xflags) { @@ -2724,7 +2716,7 @@ struct attrnames attr_secure = { .attr_get = attr_generic_get, .attr_set = attr_generic_set, .attr_remove = attr_generic_remove, - .attr_capable = attr_secure_capable, + .attr_capable = (attrcapable_t)fs_noerr, }; struct attrnames attr_user = { |