linux-toradex.git/fs/jffs2/os-linux.h, branch v3.0.42

fs: pass exact type of data dirties to ->dirty_inode

2011-05-27T11:04:40+00:00

Tell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or
anything else, so that the filesystem can track internally if it
needs to push out a transaction for fdatasync or not.

This is just the prototype change with no user for it yet.  I plan
to push large XFS changes for the next merge window, and getting
this trivial infrastructure in this window would help a lot to avoid
tree interdependencies.

Also remove incorrect comments that ->dirty_inode can't block.  That
has been changed a long time ago, and many implementations rely on it.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

convert remaining ->clear_inode() to ->evict_inode()

2010-08-09T20:48:37+00:00

Signed-off-by: Al Viro

drop unused dentry argument to ->fsync

2010-05-28T02:05:02+00:00

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

jffs2: Rename jffs2_erase_pending_trigger() to jffs2_dirty_trigger()

2010-05-19T16:15:36+00:00

Now that we do erases from GC and trigger the GC thread to do them
instead of using kupdated, this function is misnamed. It's only used
for triggering wbuf flush on NAND flash now. Rename it accordingly.

Signed-off-by: Joakim Tjernlund 
Signed-off-by: David Woodhouse

switch jffs2 to inode->i_acl

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

Signed-off-by: Al Viro

jffs2: move jffs2_write_super to super.c

2009-06-12T01:36:09+00:00

jffs2_write_super is only called from super.c and doesn't use any
functionality from fs.c.  So move it over to super.c and make it
static there.

[should go in through the vfs tree as it is a requirement for the
 next patch]

Signed-off-by: Christoph Hellwig 
Signed-off-by: Al Viro

[JFFS2] Use .unlocked_ioctl

2008-07-11T17:33:42+00:00

This changes the .ioctl to the .unlocked_ioctl version.

Signed-off-by: Stoyan Gaydarov 
Signed-off-by: David Woodhouse

[JFFS2] Invert last argument of jffs2_gc_fetch_inode(), make it boolean.

2008-05-01T16:24:28+00:00

We don't actually care about nlink; we only care whether the inode in
question is unlinked or not.

Signed-off-by: David Woodhouse

iget: stop JFFS2 from using iget() and read_inode()

2008-02-07T16:42:28+00:00

Stop the JFFS2 filesystem from using iget() and read_inode().  Replace
jffs2_read_inode() with jffs2_iget(), and call that instead of iget().
jffs2_iget() then uses iget_locked() directly and returns a proper error code
instead of an inode in the event of an error.

jffs2_do_fill_super() returns any error incurred when getting the root inode
instead of EINVAL.

Signed-off-by: David Howells 
Cc: David Woodhouse 
Acked-by: Christoph Hellwig 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[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