linux-toradex.git/fs/sysv, branch v2.6.36-rc7

fs/sysv/super.c: add support for non-PDP11 v7 filesystems

2010-08-11T04:24:18+00:00

This adds byte order autodetection (of PDP-11 and LE filesystems).  No
attempt is made to detect big-endian filesystems -- were there any?
Tested with PDP-11 v7 filesystems and PC-IX maintenance floppy.

[akpm@linux-foundation.org: coding-style fixes]
[AV: parser.h inclusion was a rudiment of discarded stuff]
Signed-off-by: Lubomir Rintel 
Cc: Christoph Hellwig 
Cc: Al Viro 
Signed-off-by: Andrew Morton 
Signed-off-by: Al Viro

V7: Adjust sanity checks for some volumes

2010-08-11T04:18:43+00:00

Newly mkfs-ed filesystems from Seventh Edition have last modification
time set to zero, but are otherwise perfectly valid.

Also, tighten up other sanity checks to filter out most filesystems with
different bytesex than we're using.

Cc: Christoph Hellwig 
Signed-off-by: Lubomir Rintel 
Signed-off-by: Al Viro

Add v7 alias

2010-08-11T04:18:42+00:00

So that the module gets autoloaded when a v7 filesystem is mounted.

Cc: Christoph Hellwig 
Signed-off-by: Lubomir Rintel 
Signed-off-by: Al Viro

sysv: do not mark superblock dirty on remount

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

No need to mark the superblock as dirty in sysv_remount, synchronize
it instead (only if mounting R/O).

I did not find any docs about this file-system, and I have no possibility
to test my changes. Thus, this is untested. I see other issues in sysv,
e.g., why sysv_sync_fs writes only in the FSTYPE_SYSV4 case? However,
it marks its SB bh's dirty for all types, and does not wait for them
ever. With zero docs I'm unable to fix this.

Signed-off-by: Artem Bityutskiy 
Signed-off-by: Al Viro

sysv: do not mark superblock dirty on mount

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

I did not find any docs about this file-system, and I have no possibility
to test my changes. Thus, this is untested.

Signed-off-by: Artem Bityutskiy 
Signed-off-by: Al Viro

switch sysv to ->evict_inode()

2010-08-09T20:47:59+00:00

Signed-off-by: Al Viro

remove inode_setattr

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

Replace inode_setattr with opencoded variants of it in all callers.  This
moves the remaining call to vmtruncate into the filesystem methods where it
can be replaced with the proper truncate sequence.

In a few cases it was obvious that we would never end up calling vmtruncate
so it was left out in the opencoded variant:

 spufs: explicitly checks for ATTR_SIZE earlier
 btrfs,hugetlbfs,logfs,dlmfs: explicitly clears ATTR_SIZE earlier
 ufs: contains an opencoded simple_seattr + truncate that sets the filesize just above

In addition to that ncpfs called inode_setattr with handcrafted iattrs,
which allowed to trim down the opencoded variant.

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

add missing setattr methods

2010-08-09T20:47:34+00:00

For the new truncate sequence every filesystem that wants to truncate on-disk
state needs a seattr method.  Convert the remaining filesystems that implement
the truncate inode operation to have its own setattr method.

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

get rid of block_write_begin_newtrunc

2010-08-09T20:47:33+00:00

Move the call to vmtruncate to get rid of accessive blocks to the callers
in preparation of the new truncate sequence and rename the non-truncating
version to block_write_begin.

While we're at it also remove several unused arguments to block_write_begin.

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

introduce __block_write_begin

2010-08-09T20:47:32+00:00

Split up the block_write_begin implementation - __block_write_begin is a new
trivial wrapper for block_prepare_write that always takes an already
allocated page and can be either called from block_write_begin or filesystem
code that already has a page allocated.  Remove the handling of already
allocated pages from block_write_begin after switching all callers that
do it to __block_write_begin.

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