linux-toradex.git/fs/jffs2/acl.h, branch v2.6.32.26

jffs2/jfs/xfs: switch over to 'check_acl' rather than 'permission()'

2009-09-08T18:09:04+00:00

This avoids an indirect call in the VFS for each path component lookup.

Well, at least as long as you own the directory in question, and the ACL
check is unnecessary.

Reviewed-by: James Morris 
Acked-by: Serge Hallyn 
Signed-off-by: Linus Torvalds

switch jffs2 to inode->i_acl

2009-06-24T12:17:05+00:00

Signed-off-by: Al Viro

[PATCH] sanitize ->permission() prototype

2008-07-27T00:53:14+00:00

* kill nameidata * argument; map the 3 bits in ->flags anybody cares
  about to new MAY_... ones and pass with the mask.
* kill redundant gfs2_iop_permission()
* sanitize ecryptfs_permission()
* fix remaining places where ->permission() instances might barf on new
  MAY_... found in mask.

The obvious next target in that direction is permission(9)

folded fix for nfs_permission() breakage from Miklos Szeredi 

Signed-off-by: Al Viro

[JFFS2] make jffs2_get_acl() static

2007-11-06T08:36:49+00:00

jffs2_get_acl() can now become static again.

Signed-off-by: Adrian Bunk 
Acked-by: KaiGai Kohei 
Signed-off-by: Andrew Morton 
Signed-off-by: David Woodhouse

[JFFS2] Tidy up fix for ACL/permissions problem.

2007-10-20T13:10:54+00:00

[In commit 9ed437c50d89eabae763dd422579f73fdebf288d we fixed a problem 
with standard permissions on newly-created inodes, when POSIX ACLs are 
enabled. This cleans it up...]

The attached patch separate jffs2_init_acl() into two parts.

The one is jffs2_init_acl_pre() called from jffs2_new_inode().
It compute ACL oriented inode->i_mode bits, and allocate in-memory ACL
objects associated with the new inode just before when inode meta
infomation is written to the medium.

The other is jffs2_init_acl_post() called from jffs2_symlink(),
jffs2_mkdir(), jffs2_mknod() and jffs2_do_create().
It actually writes in-memory ACL objects into the medium next to
the success of writing meta-information.

In the current implementation, we have to write a same inode meta
infomation twice when inode->i_mode is updated by the default ACL.
However, we can avoid the behavior by putting an updated i_mode
before it is written at first, as jffs2_init_acl_pre() doing.

Signed-off-by: KaiGai Kohei 
Signed-off-by: David Woodhouse

[JFFS2] Fix ACL vs. mode handling.

2007-08-22T11:39:19+00:00

When POSIX ACL support was enabled, we weren't writing correct
legacy modes to the medium on inode creation, or when the ACL was set.
This meant that the permissions would be incorrect after the file system
was remounted.

Signed-off-by: David Woodhouse

[JFFS2] Tidy up licensing/copyright boilerplate.

2007-04-25T13:16:47+00:00

In particular, remove the bit in the LICENCE file about contacting
Red Hat for alternative arrangements. Their errant IS department broke
that arrangement a long time ago -- the policy of collecting copyright
assignments from contributors came to an end when the plug was pulled on
the servers hosting the project, without notice or reason.

We do still dual-license it for use with eCos, with the GPL+exception
licence approved by the FSF as being GPL-compatible. It's just that nobody
has the right to license it differently.

Signed-off-by: David Woodhouse

[JFFS2][XATTR] Fix memory leak in POSIX-ACL support

2006-07-02T14:13:46+00:00

jffs2_clear_acl() which releases acl caches allocated by kmalloc()
was defined but it was never called. Thus, we faced to the risk
of memory leaking.

This patch plugs jffs2_clear_acl() into jffs2_do_clear_inode().
It ensures to release acl cache when inode is cleared.

Signed-off-by: KaiGai Kohei 
Signed-off-by: David Woodhouse

[JFFS2][XATTR] remove 'KERNEL' from acl.h

2006-05-13T06:19:36+00:00

[9/10] jffs2-xattr-v5.1-09-remove__KERNEL__.patch

Signed-off-by: KaiGai Kohei

[JFFS2][XATTR] Unify each file header part with any jffs2 file.

2006-05-13T06:18:27+00:00

Unify each file header part with any jffs2 file.

[7/10] jffs2-xattr-v5.1-07-unify_file_header.patch

Signed-off-by: KaiGai Kohei