linux.git/fs/xattr.c, branch v3.11

vfs: make lremovexattr retry once on ESTALE error

2012-12-20T23:50:11+00:00

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

vfs: make removexattr retry once on ESTALE

2012-12-20T23:50:10+00:00

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

vfs: make llistxattr retry once on ESTALE error

2012-12-20T23:50:10+00:00

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

vfs: make listxattr retry once on ESTALE error

2012-12-20T23:50:10+00:00

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

vfs: make lgetxattr retry once on ESTALE

2012-12-20T23:50:09+00:00

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

vfs: make getxattr retry once on an ESTALE error

2012-12-20T23:50:09+00:00

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

vfs: allow lsetxattr() to retry once on ESTALE errors

2012-12-20T23:50:09+00:00

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

vfs: allow setxattr to retry once on ESTALE errors

2012-12-20T23:50:08+00:00

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro

fs, xattr: fix bug when removing a name not in xattr list

2012-10-18T19:35:58+00:00

Commit 38f38657444d ("xattr: extract simple_xattr code from tmpfs") moved
some code from tmpfs but introduced a subtle bug along the way.

If the name passed to simple_xattr_remove() does not exist in the list of
xattrs, then it is possible to call kfree(new_xattr) when new_xattr is
actually initialized to itself on the stack via uninitialized_var().

This causes a BUG() since the memory was not allocated via the slab
allocator and was not bypassed through to the page allocator because it
was too large.

Initialize the local variable to NULL so the kfree() never takes place.

Reported-by: Fengguang Wu 
Signed-off-by: David Rientjes 
Acked-by: Hugh Dickins 
Acked-by: Aristeu Rozanski 
Signed-off-by: Linus Torvalds

audit: set the name_len in audit_inode for parent lookups

2012-10-12T04:32:01+00:00

Currently, this gets set mostly by happenstance when we call into
audit_inode_child. While that might be a little more efficient, it seems
wrong. If the syscall ends up failing before audit_inode_child ever gets
called, then you'll have an audit_names record that shows the full path
but has the parent inode info attached.

Fix this by passing in a parent flag when we call audit_inode that gets
set to the value of LOOKUP_PARENT. We can then fix up the pathname for
the audit entry correctly from the get-go.

While we're at it, clean up the no-op macro for audit_inode in the
!CONFIG_AUDITSYSCALL case.

Signed-off-by: Jeff Layton 
Signed-off-by: Al Viro