linux-toradex.git/fs, branch v2.6.16.31

[CIFS] Allow cifsd to suspend if connection is lost

2006-10-14T08:12:26+00:00

Make cifsd allow us to suspend if it has lost the connection with a server

Ref: http://bugzilla.kernel.org/show_bug.cgi?id=6811

Signed-off-by: Rafael J. Wysocki 
Signed-off-by: Steve French 
Signed-off-by: Adrian Bunk

[CIFS] Fix typo in earlier cifs_unlink change and protect one extra path.

2006-10-14T08:11:47+00:00

Since cifs_unlink can also be called from rename path and there
was one report of oops am making the extra check for null inode.

Signed-off-by: Steve French 
Signed-off-by: Adrian Bunk

[CIFS] Fix unlink oops when indirectly called in rename error path under heavy stress.

2006-10-14T08:11:16+00:00

Signed-off-by: Steve French 
Signed-off-by: Adrian Bunk

[CIFS] fs/cifs/dir.c: fix possible NULL dereference

2006-10-14T08:10:45+00:00

Signed-off-by: Steve French 
Signed-off-by: Adrian Bunk

fix fdset leakage

2006-10-13T15:58:30+00:00

When found, it is obvious.  nfds calculated when allocating fdsets is
rewritten by calculation of size of fdtable, and when we are unlucky, we
try to free fdsets of wrong size.

Found due to OpenVZ resource management (User Beancounters).

Signed-off-by: Alexey Kuznetsov 
Signed-off-by: Kirill Korotaev 
Signed-off-by: Adrian Bunk

Have ext2 reject file handles with bad inode numbers early.

2006-09-09T15:44:45+00:00

This prevents bad inode numbers from triggering errors in
ext2_get_inode.

Signed-off-by: Neil Brown 
Signed-off-by: Adrian Bunk

fix struct file leakage

2006-08-30T20:55:59+00:00

2.6.16 leaks like hell. While testing, I found massive filp leakage
(reproduced in openvz) in the bowels of namei.c.

Signed-off-by: Alexey Kuznetsov 
Signed-off-by: Adrian Bunk

Have ext3 reject file handles with bad inode numbers early

2006-08-30T16:01:00+00:00

blatantly ripped off from Neil Brown's ext2 patch.

Signed-off-by: Eric Sandeen 
Acked-by: "Theodore Ts'o" 
Signed-off-by: Adrian Bunk

ext3: avoid triggering ext3_error on bad NFS file handle

2006-08-30T15:58:44+00:00

The inode number out of an NFS file handle gets passed eventually to
ext3_get_inode_block() without any checking.  If ext3_get_inode_block()
allows it to trigger an error, then bad filehandles can have unpleasant
effect - ext3_error() will usually cause a forced read-only remount, or a
panic if `errors=panic' was used.

So remove the call to ext3_error there and put a matching check in
ext3/namei.c where inode numbers are read off storage.

Andrew Morton fixed an off-by-one error.

Dann Frazier ported the patch to 2.6.16.

Signed-off-by: Neil Brown 
Signed-off-by: Adrian Bunk

Fix possible UDF deadlock and memory corruption (CVE-2006-4145)

2006-08-23T16:00:30+00:00

UDF code is not really ready to handle extents larger that 1GB. This is
the easy way to forbid creating those.

Also truncation code did not count with the case when there are no
extents in the file and we are extending the file.

Signed-off-by: Jan Kara 
Signed-off-by: Adrian Bunk