linux-toradex.git/fs/cramfs, branch v3.0.95

cramfs: get_cramfs_inode() returns ERR_PTR() on failure

2011-07-18T03:22:02+00:00

... and we want to report these failures in ->lookup() anyway.

Signed-off-by: Al Viro

cramfs: generate unique inode number for better inode cache usage

2011-01-13T16:03:23+00:00

Generate a unique inode numbers for any entries in the cram file system.
For files which did not contain data's (device nodes, fifos and sockets)
the offset of the directory entry inside the cramfs plus 1 will be used as
inode number.

The + 1 for the inode will it make possible to distinguish between a file
which contains no data and files which has data, the later one has a inode
value where the lower two bits are always 0.

It also reimplements the behavior to set the size and the number of block
to 0 for special file, which is the right value for empty files, devices,
fifos and sockets

As a little benefit it will be also more compatible which older mkcramfs,
because it will never use the cramfs_inode->offset for creating a inode
number for special files.

[akpm@linux-foundation.org: trivial comment fix]
[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Stefani Seibold 
Cc: Al Viro 
Cc: Pekka Enberg 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

new helper: mount_bdev()

2010-10-29T08:16:13+00:00

... and switch of the obvious get_sb_bdev() users to ->mount()

Signed-off-by: Al Viro

cramfs: only unlock new inodes

2010-08-18T05:01:33+00:00

Commit 77b8a75f5bb introduced a warning at fs/inode.c:692 unlock_new_inode(),
caused by unlock_new_inode() being called on existing inodes as well.

This patch changes setup_inode() to only call unlock_new_inode() for I_NEW
inodes.

Signed-off-by: Alexander Shishkin 
Signed-off-by: Al Viro

simplify get_cramfs_inode()

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

simply don't hash the inodes that don't have real inumber instead of
skipping them during iget5_locked(); as the result, simple iget_locked()
would do and we can get rid of cramfs ->drop_inode() as well.

Signed-off-by: Al Viro

fs/cramfs: return f_fsid for statfs(2)

2009-04-03T02:05:08+00:00

Make cramfs return f_fsid info for statfs(2).

Signed-off-by: Coly Li 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

cramfs: propagate uncompression errors

2009-04-03T02:05:07+00:00

Decompression errors can arise due to corruption of compressed blocks on
flash or in memory.  This patch propagates errors detected during
decompression back to the block layer.

Signed-off-by: David VomLehn 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

fs/Kconfig: move cramfs out

2009-01-22T10:15:58+00:00

Signed-off-by: Alexey Dobriyan

zero i_uid/i_gid on inode allocation

2009-01-05T16:54:28+00:00

... and don't bother in callers.  Don't bother with zeroing i_blocks,
while we are at it - it's already been zeroed.

i_mode is not worth the effort; it has no common default value.

Signed-off-by: Al Viro

cramfs: fix named-pipe handling

2008-08-20T22:40:32+00:00

After commit a97c9bf33f4612e2aed6f000f6b1d268b6814f3c (fix cramfs
making duplicate entries in inode cache) in kernel 2.6.14, named-pipe
on cramfs does not work properly.

It seems the commit make all named-pipe on cramfs share their inode
(and named-pipe buffer).

Make ..._test() refuse to merge inodes with ->i_ino == 1, take inode setup
back to get_cramfs_inode() and make ->drop_inode() evict ones with ->i_ino
== 1 immediately.

Reported-by: Atsushi Nemoto 
Cc: Al Viro 
Cc: 		[2.6.14 and later]
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds