linux.git/fs, branch v2.6.33

fs/exec.c: fix initial stack reservation

2010-02-23T03:50:34+00:00

803bf5ec259941936262d10ecc84511b76a20921 ("fs/exec.c: restrict initial
stack space expansion to rlimit") attempts to limit the initial stack to
20*PAGE_SIZE.  Unfortunately, in attempting ensure the stack is not
reduced in size, we ended up not changing the stack at all.

This size reduction check is not necessary as the expand_stack call does
this already.

This caused a regression in UML resulting in most guest processes being
killed.

Signed-off-by: Michael Neuling 
Reviewed-by: KOSAKI Motohiro 
Acked-by: WANG Cong 
Cc: Anton Blanchard 
Cc: Oleg Nesterov 
Cc: James Morris 
Cc: Serge Hallyn 
Cc: Benjamin Herrenschmidt 
Cc: Jouni Malinen 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

CacheFiles: Fix a race in cachefiles_delete_object() vs rename

2010-02-20T15:06:35+00:00

cachefiles_delete_object() can race with rename.  It gets the parent directory
of the object it's asked to delete, then locks it - but rename may have changed
the object's parent between the get and the completion of the lock.

However, if such a circumstance is detected, we abandon our attempt to delete
the object - since it's no longer in the index key path, it won't be seen
again by lookups of that key.  The assumption is that cachefilesd may have
culled it by renaming it to the graveyard for later destruction.

Signed-off-by: David Howells 
Signed-off-by: Al Viro

vfs: don't call ima_file_check() unconditionally in nfsd_open()

2010-02-20T05:47:31+00:00

commit 1e41568d7378d1ba8c64ba137b9ddd00b59f893a ("Take ima_path_check()
in nfsd past dentry_open() in nfsd_open()") moved this code back to its
original location but missed the "else".

Signed-off-by: Chuck Ebbert 
Signed-off-by: Al Viro

Switch proc/self to nd_set_link()

2010-02-19T15:25:41+00:00

Signed-off-by: Al Viro

fix LOOKUP_FOLLOW on automount "symlinks"

2010-02-19T08:56:42+00:00

Make sure that automount "symlinks" are followed regardless of LOOKUP_FOLLOW;
it should have no effect on them.

Cc: stable@kernel.org
Signed-off-by: Al Viro

sysfs: sysfs_sd_setattr set iattrs unconditionally

2010-02-16T23:42:42+00:00

There is currently a bug in sysfs_sd_setattr inherited from
sysfs_setattr in 2.6.32 where the first time we set the attributes
on a sysfs file we allocate backing store but do not set the
backing store attributes.  Resulting in overly restrictive
permissions on sysfs files.

The fix is to simply modify the code so that it always executes
when we update the sysfs attributes, as we did in 2.6.31 and earlier.

Signed-off-by: Eric W. Biederman 
Tested-by: Jean Delvare 
Cc: stable 
Signed-off-by: Greg Kroah-Hartman

Merge git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable

2010-02-16T03:56:21+00:00

* git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable:
  Btrfs: btrfs_mark_extent_written uses the wrong slot

NFS: Too many GETATTR and ACCESS calls after direct I/O

2010-02-16T03:53:43+00:00

The cached read and write paths initialize fattr->time_start in their
setup procedures.  The value of fattr->time_start is propagated to
read_cache_jiffies by nfs_update_inode().  Subsequent calls to
nfs_attribute_timeout() will then use a good time stamp when
computing the attribute cache timeout, and squelch unneeded GETATTR
calls.

Since the direct I/O paths erroneously leave the inode's
fattr->time_start field set to zero, read_cache_jiffies for that inode
is set to zero after any direct read or write operation.  This
triggers an otw GETATTR or ACCESS call to update the file's attribute
and access caches properly, even when the NFS READ or WRITE replies
have usable post-op attributes.

Make sure the direct read and write setup code performs the same fattr
initialization as the cached I/O paths to prevent unnecessary GETATTR
calls.

This was likely introduced by commit 0e574af1 in 2.6.15, which appears
to add new nfs_fattr_init() call sites in the cached read and write
paths, but not in the equivalent places in fs/nfs/direct.c.  A
subsequent commit in the same series, 33801147, introduces the
fattr->time_start field.

Interestingly, the direct write reschedule path already has a call to
nfs_fattr_init() in the right place.

Reported-by: Quentin Barnes 
Signed-off-by: Chuck Lever 
Cc: stable@kernel.org
Signed-off-by: Trond Myklebust 
Signed-off-by: Linus Torvalds

Merge branch 'reiserfs/kill-bkl' of git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing

2010-02-16T03:51:45+00:00

* 'reiserfs/kill-bkl' of git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing:
  reiserfs: Fix softlockup while waiting on an inode

reiserfs: Fix softlockup while waiting on an inode

2010-02-14T18:07:56+00:00

When we wait for an inode through reiserfs_iget(), we hold
the reiserfs lock. And waiting for an inode may imply waiting
for its writeback. But the inode writeback path may also require
the reiserfs lock, which leads to a deadlock.

We just need to release the reiserfs lock from reiserfs_iget()
to fix this.

Reported-by: Alexander Beregalov 
Signed-off-by: Frederic Weisbecker 
Tested-by: Christian Kujau 
Cc: Chris Mason