diff options
| author | Evgeniy Dushistov <dushistov@mail.ru> | 2007-04-17 01:53:24 -0400 |
|---|---|---|
| committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-04-17 19:36:27 -0400 |
| commit | 07a0cfec30848319cc86f21cce0d2efeca593e1a (patch) | |
| tree | adf05a9b27e8298f0b8f810b5b2979f33350f097 /lib/bitrev.c | |
| parent | 3d2c5b415ccd6c322e18adaed3a5b21f7ec555ef (diff) | |
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>
Diffstat (limited to 'lib/bitrev.c')
0 files changed, 0 insertions, 0 deletions