[Bug 1964] New: HPFS crash on writing

[Martin J. Bligh]

http://bugme.osdl.org/show_bug.cgi?id=1964

           Summary: HPFS crash on writing
    Kernel Version: 2.6.1
            Status: NEW
          Severity: high
             Owner: fs_other@xxxxxxxxxxxxxxxxxxxx
         Submitter: relf@xxxxxxxxxx


Distribution: Debian unstable, kernel 2.6.1
Problem Description: HPFS driver crashes on attempt to write. Reproduced on two
different systems/partitions.

Steps to reproduce: mount some HPFS partition, try to write something on it.
You'll get something like

kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000002c
kernel:  printing eip:
kernel: c01e3919
kernel: *pde = 00000000
kernel: Oops: 0002 [#1]
kernel: CPU:    0
kernel: EIP:    0060:[hpfs_lock_2inodes+41/112]    Not tainted
kernel: EFLAGS: 00010283
kernel: EIP is at hpfs_lock_2inodes+0x29/0x70
kernel: eax: 015eed65   ebx: f5b8d084   ecx: 0000002c   edx: 015dbffc
kernel: esi: f5b8d084   edi: ebff5b00   ebp: 00000000   esp: eedd3eb4
kernel: ds: 007b   es: 007b   ss: 0068
kernel: Process mc (pid: 610, threadinfo=eedd2000 task=f401a6f0)
kernel: Stack: 00000000 c01ed687 f59d2cc4 f5b8d084 ebff5b80 0000000b f5294000
0000000b
kernel:        f59d2c80 ebff5b80 0000000b 0000000b eedd3f88 c0173abf f586ad40
ebff5b68
kernel:        eedd3f88 f7f7b37c 090dcff9 eedd2000 e9f6bf30 00000000 ebff5b00
f5294000
kernel: Call Trace:
kernel:  [hpfs_unlink+135/1120] hpfs_unlink+0x87/0x460
kernel:  [__d_lookup+351/368] __d_lookup+0x15f/0x170
kernel:  [cached_lookup+35/144] cached_lookup+0x23/0x90
kernel:  [permission+47/80] permission+0x2f/0x50
kernel:  [vfs_unlink+205/400] vfs_unlink+0xcd/0x190
kernel:  [sys_unlink+204/320] sys_unlink+0xcc/0x140
kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
kernel:
kernel: Code: f0 ff 0d 2c 00 00 00 0f 88 7f 07 00 00 f0 ff 0d 2c 00 00 00

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