Evgeniy Dushistov 07a0cfec30 ufs proper handling of zero link case
This patch should fix or partly fix this bug:
http://bugzilla.kernel.org/show_bug.cgi?id=8276

The problem is:

- if we see "zero link case" during reading inode operation, we call
  ufs_error(which remount fs readonly), but not "mark" inode as bad (1)

- in readonly case we do not fill some data structures, which are used in
  read and write case (2)

- VFS call ufs_delete_inode if link count is zero (3)

so (1)->(3)->(2) cause oops, this patch should fix such scenario

Signed-off-by: Evgeniy Dushistov <dushistov@mail.ru>
Cc: Jim Paris <jim@jtan.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-04-17 16:36:27 -07:00
..
2007-02-20 17:10:15 -08:00
2007-04-15 16:48:11 -07:00
2007-04-17 16:36:27 -07:00
2006-01-11 18:42:13 -08:00
2005-04-16 15:20:36 -07:00
2005-04-16 15:20:36 -07:00
2006-10-04 06:51:26 -06:00
2007-03-06 09:30:25 -08:00
2006-12-07 08:39:25 -08:00
2006-04-11 13:53:33 +02:00
2007-02-17 16:10:59 -05:00
2006-12-07 08:39:25 -08:00
2007-02-17 21:30:15 -05:00
2006-10-01 00:39:19 -07:00
2005-04-16 15:20:36 -07:00
2006-03-23 07:38:11 -08:00
2007-03-29 14:26:42 +02:00