linux-toradex.git/fs/jffs2/xattr.c, branch v3.9.4

jffs2: allow to complete xattr integrity check on first GC scan

2012-05-14T04:32:36+00:00

Unlike file data integrity the xattr data integrity was not checked
before some explicit access to the attribute was made.

This could leave in the system a number of corrupted extended attributes
which will be detected only at access time and possibly at a very late
time compared to the time the corruption actually happened.

This patch adds the ability to check for extended attribute integrity
on first GC scan pass (similar to file data integrity check). This allows
for all present attributes to be completly verified before any use of them.

In order to work correctly this patch also needs the patch allowing
JFFS2 to discriminate between recoverable and non recoverable errors
on extended attributes.

Signed-off-by: Jean-Christophe DUBOIS 
Signed-off-by: Artem Bityutskiy 
Signed-off-by: David Woodhouse

jffs2: allow to discriminate between recoverable and non-recoverable errors

2012-05-14T04:30:34+00:00

This patch is basically a revert of commit f326966b3df47f4fa7e90425f60efdd30c31fe19.

It allows JFFS2 to make the distinction between a potential transient
error (reading or writing the media) and a non recoverable error like a
bad CRC on the extended attribute data or some insconsitent parameters.

In order to make clear that the error is indeed intended to report a
corrupted attribute, a new local error code (JFFS2_XATTR_IS_CORRUPTED)
is introduced rather than returning a confusing positive EIO, which is
what led to the inappropriate "fix" last time.

This error code is never reported to user space and only checked locally
in this file.

Signed-off-by: Jean-Christophe DUBOIS 
Signed-off-by: Artem Bityutskiy 
Signed-off-by: David Woodhouse

jffs2: Standardize JFFS_ uses

2012-03-26T23:42:14+00:00

Use pr_ to prefix KBUILD_MODNAME via pr_fmt.

Remove obfuscating defines and use constants in pr_
No need for a do {} while (0) for single statements.

Form of JFFS_ output changes from
"JFFS2 notice: " to "jffs2: notice: "

Added pr_fmt to xattr.c

Signed-off-by: Joe Perches 
Signed-off-by: Artem Bityutskiy 
Signed-off-by: David Woodhouse

jffs2: remove a trailing white space in commentaries

2011-03-11T14:22:48+00:00

Signed-off-by: Tracey Dent 
Signed-off-by: Artem Bityutskiy 
Signed-off-by: David Woodhouse

jffs2: fix error value sign

2010-12-03T16:30:08+00:00

do_verify_xattr_datum(), do_load_xattr_datum(), load_xattr_datum()
and verify_xattr_ref() should return negative value on error.
Sometimes they return EIO that is positive.  Change this to -EIO.

Signed-off-by: Vasiliy Kulikov 
Signed-off-by: Artem Bityutskiy 
Signed-off-by: David Woodhouse

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

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

Signed-off-by: Al Viro

Fix up trivial spelling errors ('taht' -> 'that')

2010-07-21T16:25:42+00:00

Pointed out by Lucas who found the new one in a comment in
setup_percpu.c. And then I fixed the others that I grepped
for.

Reported-by: Lucas 
Signed-off-by: Linus Torvalds

jffs2: constify xattr_handler

2010-05-21T22:31:20+00:00

Signed-off-by: Stephen Hemminger 
Signed-off-by: Al Viro

sanitize xattr handler prototypes

2009-12-16T17:16:49+00:00

Add a flags argument to struct xattr_handler and pass it to all xattr
handler methods.  This allows using the same methods for multiple
handlers, e.g. for the ACL methods which perform exactly the same action
for the access and default ACLs, just using a different underlying
attribute.  With a little more groundwork it'll also allow sharing the
methods for the regular user/trusted/secure handlers in extN, ocfs2 and
jffs2 like it's already done for xfs in this patch.

Also change the inode argument to the handlers to a dentry to allow
using the handlers mechnism for filesystems that require it later,
e.g. cifs.

[with GFS2 bits updated by Steven Whitehouse ]

Signed-off-by: Christoph Hellwig 
Reviewed-by: James Morris 
Acked-by: Joel Becker 
Signed-off-by: Al Viro

tree-wide: fix assorted typos all over the place

2009-12-04T14:39:55+00:00

That is "success", "unknown", "through", "performance", "[re|un]mapping"
, "access", "default", "reasonable", "[con]currently", "temperature"
, "channel", "[un]used", "application", "example","hierarchy", "therefore"
, "[over|under]flow", "contiguous", "threshold", "enough" and others.

Signed-off-by: André Goddard Rosa 
Signed-off-by: Jiri Kosina