linux-toradex.git/fs/inode.c, branch v3.4.23

trim includes in inode.c

2012-03-21T01:29:51+00:00

Signed-off-by: Al Viro

switch touch_atime to struct path

2012-03-21T01:29:41+00:00

Signed-off-by: Al Viro

vfs: turn generic_drop_inode() into static inline

2012-03-21T01:29:33+00:00

Once upon a time it used to be much bigger, but these days there's
no point whatsoever keeping it in fs/inode.c, especially since
it's not even needed as initializer for ->drop_inode() - it's the
default and leaving ->drop_inode NULL will do just as well.

Signed-off-by: Al Viro

restore smp_mb() in unlock_new_inode()

2012-03-10T22:07:28+00:00

wait_on_inode() doesn't have ->i_lock

Signed-off-by: Al Viro

vfs: Correctly set the dir i_mutex lockdep class

2012-03-10T21:05:38+00:00

9a7aa12f3911853a introduced additional logic around setting the i_mutex
lockdep class for directory inodes. The idea was that some filesystems
may want their own special lockdep class for different directory
inodes and calling unlock_new_inode() should not clobber one of
those special classes.

I believe that the added conditional, around the *negated* return value
of lockdep_match_class(), caused directory inodes to be placed in the
wrong lockdep class.

inode_init_always() sets the i_mutex lockdep class with i_mutex_key for
all inodes. If the filesystem did not change the class during inode
initialization, then the conditional mentioned above was false and the
directory inode was incorrectly left in the non-directory lockdep class.
If the filesystem did set a special lockdep class, then the conditional
mentioned above was true and that class was clobbered with
i_mutex_dir_key.

This patch removes the negation from the conditional so that the i_mutex
lockdep class is properly set for directory inodes. Special classes are
preserved and directory inodes with unmodified classes are set with
i_mutex_dir_key.

Signed-off-by: Tyler Hicks 
Reviewed-by: Jan Kara 
Signed-off-by: Al Viro

vfs: fix panic in __d_lookup() with high dentry hashtable counts

2012-02-14T01:45:38+00:00

When the number of dentry cache hash table entries gets too high
(2147483648 entries), as happens by default on a 16TB system, use of a
signed integer in the dcache_init() initialization loop prevents the
dentry_hashtable from getting initialized, causing a panic in
__d_lookup().  Fix this in dcache_init() and similar areas.

Signed-off-by: Dimitri Sivanich 
Acked-by: David S. Miller 
Cc: Al Viro 
Signed-off-by: Andrew Morton 
Signed-off-by: Al Viro

vfs: remove printk from set_nlink()

2012-01-17T21:39:47+00:00

Don't log a message for set_nlink(0).

Signed-off-by: Miklos Szeredi 
Signed-off-by: Al Viro

mm: account reaped page cache on inode cache pruning

2012-01-11T00:30:42+00:00

Inode cache pruning indirectly reclaims page-cache by invalidating mapping
pages.  Let's account them into reclaim-state to notice this progress in
memory reclaimer.

Signed-off-by: Konstantin Khlebnikov 
Cc: Dave Chinner 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

vfs: count unlinked inodes

2012-01-07T04:20:12+00:00

Add a new counter to the superblock that keeps track of unlinked but
not yet deleted inodes.

Do not WARN_ON if set_nlink is called with zero count, just do a
ratelimited printk.  This happens on xfs and probably other
filesystems after an unclean shutdown when the filesystem reads inodes
which already have zero i_nlink.  Reported by Christoph Hellwig.

Signed-off-by: Miklos Szeredi 
Tested-by: Toshiyuki Okajima 
Signed-off-by: Al Viro

switch inode_init_owner() to umode_t

2012-01-04T03:55:11+00:00

Signed-off-by: Al Viro