2.2.6 ext2 kernel oops

don@sabotage.org
Thu, 6 May 1999 02:25:52 +0200 (CEST)


I was doing some tar operations on a failing scsi device (lots of errors)
using 2.2.6 and managed to get the following kernel oops. Missing code to
check error conditions?

scsi0: MEDIUM ERROR on channel 0, id 4, lun 0, CDB: Read (6) 1b 00 53 02 00
Current error sd08:01: sense key Medium Error
Additional sense indicates Unrecovered read error
scsidisk I/O error: dev 08:01, sector 1769492
EXT2-fs error (device sd(8,1)): read_block_bitmap: Cannot read block bitmap - block_group = 108, block_bitmap = 884746
tar: usr/bin/orbit-idl: Could not write to file: Input/output error
usr/bin/orbit-ird
Unable to handle kernel NULL pointer dereference at virtual address 00000024
current->tss.cr3 = 07394000, %cr3 = 07394000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0144ae8>]
EFLAGS: 00010246
eax: 0000006c ebx: 00000000 ecx: 00000000 edx: c706f800
esi: c1999ed0 edi: c706f800 ebp: 000d4001 esp: c2d2de00
ds: 0018 es: 0018 ss: 0018
Process tar (pid: 364, process nr: 26, stackpage=c2d2d000)
Stack: c2d2df14 000d4001 000d799e c62f8660 00000001 c706f800 000d8000 00000000
00000801 000d799e 00000400 c6fd2800 c6fd5980 000d799e 0000006c 00000000
c7534f20 c0146e8c c1999ed0 000d4001 c1999fd4 c1999fd0 c2d2df14 ffffffff
Call Trace: [<c0146e8c>] [<c01471ee>] [<c01475f3>] [<c0145ad5>] [<c01458f0>] [<c0129747>] [<c0148aaa>]
[<c012ea48>] [<c0112804>] [<c012e30e>] [<c011275c>] [<c0127c8f>] [<c0108d14>]
Code: 8b 73 24 8b 4a 54 c1 e9 03 89 f5 74 0c 89 f7 31 c0 fc f2 ae
Broken pipe

While I've got the attention of anyone that might be into ext2 filesystem,
let me take this chance to say that there are several alternatives to the
"capability" system that's gotten some attention lately. So those of you
who are writing a new filesystem, please don't neglect the opportunity to
make accomodations for security improvements other than capabilities. (which
personally I think are misguided because of their inadequacy, but to each
their own)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/