I can create a filesystem with a block size of 512bytes but as soon as it is filled by 28MB a kernel panic occurs. I've been able to reproduce it on 3 machines (two ~x86, one sparc) Steps to reproduce: dd if=/dev/zero of=/tmp/file.iso bs=1M count=600 losetup /dev/loop0 /tmp/file.iso mkreiserfs -b 512 /dev/loop0 ##mounting without -t gives: Floating point exception mount -t reiserfs /dev/loop0 /tmp/portage cp -r /usr/portage/* /tmp/portage/ kernel panic: ReiserFS: loop0: found reiserfs format "3.6" with standard journal ReiserFS: loop0: using ordered data mode ReiserFS: loop0: journal params: device loop0, size 3965, journal first block 130, max trans len 128, max batch 112, max commit age 30, max trans age 30 ReiserFS: loop0: checking transaction log (loop0) ReiserFS: loop0: Using r5 hash to sort names ReiserFS: loop0: warning: vs-8111: get_num_ver: split_item_position is out of boundary BUG: unable to handle kernel NULL pointer dereference at virtual address 0000000e printing eip: c019cb2b *pde = 00000000 Oops: 0000 [#1] PREEMPT SMP Modules linked in: CPU: 0 EIP: 0060:[<c019cb2b>] Tainted: P VLI EFLAGS: 00010202 (2.6.18-ck1 #2) EIP is at check_balance+0x941/0x12bd eax: 00000004 ebx: 00000006 ecx: f4e71aae edx: c03cfae0 esi: f4e71b64 edi: 00000000 ebp: 00000600 esp: f4e71a10 ds: 007b es: 007b ss: 0068 Process cp (pid: 5275, ti=f4e70000 task=f77ba030 task.ti=f4e70000) Stack: 00000000 ffffffff 00000000 ffffffff f4e71aa8 00000001 00000003 00000054 00000028 00000000 00000600 016169c4 e86169c4 00000418 00000000 00000000 00000001 00000002 00000000 00000001 e86169c4 00000000 f4e71cd4 00000004 Call Trace: [<c0157852>] ll_rw_block+0x33/0xa4 [<c01a672d>] search_by_key+0x14f/0xf9b [<c019d64a>] fix_nodes+0x1a3/0x754 [<c01a96e4>] reiserfs_insert_item+0x163/0x312 [<c01998d7>] reiserfs_file_write+0x1475/0x1d5c [<c013aaba>] generic_file_read+0xa2/0xc5 [<c012ba7e>] autoremove_wake_function+0x0/0x37 [<c014881d>] do_mmap_pgoff+0x4d1/0x6b4 [<c01554b6>] vfs_write+0x8b/0x147 [<c0198462>] reiserfs_file_write+0x0/0x1d5c [<c0155b0e>] sys_write+0x41/0x6a [<c0102c1d>] sysenter_past_esp+0x56/0x79 Code: 00 8b 4c 24 4c 31 d2 89 f0 e8 70 e4 ff ff e9 83 f7 ff ff 89 f0 e8 d9 e4 ff ff 85 c0 8d 74 26 00 0f 84 a3 f8 ff ff e9 6b f7 ff ff <0f> bf 43 08 c7 44 24 14 01 00 00 00 8d 94 24 a2 00 00 00 89 54 EIP: [<c019cb2b>] check_balance+0x941/0x12bd SS:ESP 0068:f4e71a10 BUG: warning at kernel/exit.c:853/do_exit() [<c011d37c>] do_exit+0x7fa/0x8d3 [<c0190068>] do_balance+0x2fc1/0x32b9 [<c01040c9>] do_trap+0x0/0xb4 [<c01121bb>] do_page_fault+0x275/0x56b [<c0111f46>] do_page_fault+0x0/0x56b [<c0103751>] error_code+0x39/0x40 [<c019cb2b>] check_balance+0x941/0x12bd [<c0157852>] ll_rw_block+0x33/0xa4 [<c01a672d>] search_by_key+0x14f/0xf9b [<c019d64a>] fix_nodes+0x1a3/0x754 [<c01a96e4>] reiserfs_insert_item+0x163/0x312 [<c01998d7>] reiserfs_file_write+0x1475/0x1d5c [<c013aaba>] generic_file_read+0xa2/0xc5 [<c012ba7e>] autoremove_wake_function+0x0/0x37 [<c014881d>] do_mmap_pgoff+0x4d1/0x6b4 [<c01554b6>] vfs_write+0x8b/0x147 [<c0198462>] reiserfs_file_write+0x0/0x1d5c [<c0155b0e>] sys_write+0x41/0x6a [<c0102c1d>] sysenter_past_esp+0x56/0x79
Created attachment 99100 [details] emerge --info emerge --info of my testing-machines
Is this reproducible on the latest development kernel? currently 2.6.19-rc1
Works like a charm on sys-kernel/vanilla-sources-2.6.19_rc1.
