linux.git/fs/inode.c, branch v2.6.35-rc4

vfs: Add inode uid,gid,mode init helper

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

Signed-off-by: Dmitry Monakhov 
Signed-off-by: Al Viro

fs: inode.c use atomic_inc_return in __iget

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

Using atomic_inc_return in __iget(struct inode *inode) makes the intent
of this code clearer and generates less code on processors that have
this operation.

On x86_64 this patch reduces the text size of inode.o by 12 bytes.

Signed-off-by: Richard Kennedy 

----
patch against 2.6.34-rc7
compiled & tested on x86_64 AMD X2

I've been running with this patch applied for several weeks with no
obvious problems.
regards
Richard
Signed-off-by: Al Viro

security: remove dead hook inode_delete

2010-04-12T02:19:15+00:00

Unused hook.  Remove.

Signed-off-by: Eric Paris 
Signed-off-by: James Morris

dquot: move dquot initialization responsibility into the filesystem

2010-03-04T23:20:30+00:00

Currently various places in the VFS call vfs_dq_init directly.  This means
we tie the quota code into the VFS.  Get rid of that and make the
filesystem responsible for the initialization.   For most metadata operations
this is a straight forward move into the methods, but for truncate and
open it's a bit more complicated.

For truncate we currently only call vfs_dq_init for the sys_truncate case
because open already takes care of it for ftruncate and open(O_TRUNC) - the
new code causes an additional vfs_dq_init for those which is harmless.

For open the initialization is moved from do_filp_open into the open method,
which means it happens slightly earlier now, and only for regular files.
The latter is fine because we don't need to initialize it for operations
on special files, and we already do it as part of the namespace operations
for directories.

Add a dquot_file_open helper that filesystems that support generic quotas
can use to fill in ->open.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Jan Kara

dquot: move dquot drop responsibility into the filesystem

2010-03-04T23:20:29+00:00

Currently clear_inode calls vfs_dq_drop directly.  This means
we tie the quota code into the VFS.  Get rid of that and make the
filesystem responsible for the drop inside the ->clear_inode
superblock operation.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Jan Kara

kill I_LOCK

2009-12-17T16:03:25+00:00

After I_SYNC was split from I_LOCK the leftover is always used together with
I_NEW and thus superflous.

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

LSM: imbed ima calls in the security hooks

2009-10-25T04:22:48+00:00

Based on discussions on LKML and LSM, where there are consecutive
security_ and ima_ calls in the vfs layer, move the ima_ calls to
the existing security_ hooks.

Signed-off-by: Mimi Zohar 
Signed-off-by: James Morris

vfs: optimize touch_time() too

2009-09-24T11:47:27+00:00

Do a similar optimization as earlier for touch_atime.  Getting the lock in
mnt_get_write is relatively costly, so try all avenues to avoid it first.

This patch is careful to still only update inode fields inside the lock
region.

This didn't show up in benchmarks, but it's easy enough to do.

[akpm@linux-foundation.org: fix typo in comment]
[hugh.dickins@tiscali.co.uk: fix inverted test of mnt_want_write_file()]
Signed-off-by: Andi Kleen 
Cc: Christoph Hellwig 
Cc: Valerie Aurora 
Cc: Al Viro 
Cc: Dave Hansen 
Signed-off-by: Hugh Dickins 
Signed-off-by: Andrew Morton 
Signed-off-by: Al Viro

vfs: optimization for touch_atime()

2009-09-24T11:47:26+00:00

Some benchmark testing shows touch_atime to be high up in profile logs for
IO intensive workloads.  Most likely that's due to the lock in
mnt_want_write().  Unfortunately touch_atime first takes the lock, and
then does all the other tests that could avoid atime updates (like noatime
or relatime).

Do it the other way round -- first try to avoid the update and only then
if that didn't succeed take the lock.  That works because none of the
atime avoidance tests rely on locking.

This also eliminates a goto.

Signed-off-by: Andi Kleen 
Cc: Christoph Hellwig 
Reviewed-by: Valerie Aurora 
Cc: Al Viro 
Cc: Dave Hansen 
Signed-off-by: Andrew Morton 
Signed-off-by: Al Viro

vfs: split generic_forget_inode() so that hugetlbfs does not have to copy it

2009-09-24T11:47:25+00:00

Hugetlbfs needs to do special things instead of truncate_inode_pages().
 Currently, it copied generic_forget_inode() except for
truncate_inode_pages() call which is asking for trouble (the code there
isn't trivial).  So create a separate function generic_detach_inode()
which does all the list magic done in generic_forget_inode() and call
it from hugetlbfs_forget_inode().

Signed-off-by: Jan Kara 
Cc: Al Viro 
Cc: Christoph Hellwig 
Signed-off-by: Andrew Morton 
Signed-off-by: Al Viro