oops in current->journal-info in ext3 and reiserfs
Hello , I am seeing oopses in ext3 and also in reiserfs because of invalid current->journal_info. I am facing this problem in kernel 2.4.21-143-numa. This is on suse 8.1 amd64. Oops IS WITH IN ext3. The test i am using creates files in ext3 and our filesystem, which is network based, and comparing results in both, and tripping on this oops from time to time. Our filesystem does not modify the journal_info in any way. Is there any workaround for this ? or a possible patch ? Any help is muchly appreciated > Error (regular_file): read_system_map stat /boot/System.map-2.4.21-143-numa
failed Jun 17 14:48:11 porting-10 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000000002ae Jun 17 14:48:11 porting-10 kernel: ffffffffa0000616 Jun 17 14:48:11 porting-10 kernel: PML4 1d4d5067 PGD 0 Jun 17 14:48:11 porting-10 kernel: Oops: 0000 Jun 17 14:48:11 porting-10 kernel: CPU 0 Jun 17 14:48:11 porting-10 kernel: Pid: 15951, comm: detect_corrupti Tainted: P Jun 17 14:48:11 porting-10 kernel: RIP: 0010:[<ffffffffa0000616>]{:jbd:journal_start_Rsmp_2c291b1f+54} Using defaults from ksymoops -t elf64-x86-64 -a i386:x86-64 Jun 17 14:48:11 porting-10 kernel: RSP: 0018:000001001c643e58 EFLAGS: 00010202 Jun 17 14:48:11 porting-10 kernel: RAX: ffffffffffffffe2 RBX: 00000000000002ae RCX: 000001002475ae40 Jun 17 14:48:11 porting-10 kernel: RDX: 0000000000000000 RSI: 0000000000000003 RDI: 000001003fd21e00 Jun 17 14:48:11 porting-10 kernel: RBP: 000001003fd21e00 R08: 00000000000003e8 R09: 000000000001e660 Jun 17 14:48:11 porting-10 kernel: R10: 0000000040621ef0 R11: 0000000000000202 R12: 000001001c643ee8 Jun 17 14:48:11 porting-10 kernel: R13: 0000000000000048 R14: 0000000000000000 R15: 0000000040606340 Jun 17 14:48:11 porting-10 kernel: FS: 0000000000000000(0000) GS:ffffffff804bd740(0000) knlGS:0000000000000000 Jun 17 14:48:11 porting-10 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Jun 17 14:48:11 porting-10 kernel: CR2: 00000000000002ae CR3: 0000000000101000 CR4: 00000000000006e0 Jun 17 14:48:11 porting-10 kernel: Process detect_corrupti (pid: 15951, stackpage=1001c643000) Jun 17 14:48:11 porting-10 kernel: Stack: 000001001c643e58 0000000000000018 000001001c643ee8 0000010013ce6b40 Jun 17 14:48:11 porting-10 kernel: 0000000000000000 0000010013ce6b40 ffffffffa0018366 000001003c1a7b80 Jun 17 14:48:11 porting-10 kernel: 000001001c643ee8 0000010013ce6b40 0000010013ce6b40 0000000000000048 Jun 17 14:48:11 porting-10 kernel: Call Trace: [<ffffffffa0018366>]{:ext3:ext3_setattr+566} Jun 17 14:48:11 porting-10 kernel: [<ffffffff801746d7>]{notify_change+135} [<ffffffff80152d15>]{do_truncate+165} Jun 17 14:48:11 porting-10 kernel: [<ffffffff801530c3>]{sys_ftruncate+259} [<ffffffff80110093>]{system_call+119} Jun 17 14:48:11 porting-10 kernel: Code: 48 8b 03 48 39 38 74 34 49 c7 c0 c0 a6 00 a0 b9 fa 00 00 00
RIP; ffffffffa0000616 <[jbd]journal_start+36/f0> <=====
RAX; ffffffffffffffe2 <END_OF_CODE+5f88f2c3/????> >>RCX; 000001002475ae40 Before first symbol >>RDI; 000001003fd21e00 Before first symbol >>RBP; 000001003fd21e00 Before first symbol >>R09; 000000000001e660 Before first symbol >>R10; 0000000040621ef0 Before first symbol >>R12; 000001001c643ee8 Before first symbol >>R15; 0000000040606340 Before first symbol
Trace; ffffffffa0018366 <[ext3]ext3_setattr+236/420> Trace; ffffffff801746d7 <notify_change+87/360> Trace; ffffffff801530c3 <sys_ftruncate+103/130>
Code; ffffffffa0000616 <[jbd]journal_start+36/f0> 0000000000000000 <_RIP>: Code; ffffffffa0000616 <[jbd]journal_start+36/f0> <===== Code; ffffffffa0000616 <[jbd]journal_start+36/f0> 0000000000000000 <_RIP>: Code; ffffffffa0000616 <[jbd]journal_start+36/f0> <===== 0: 48 8b 03 mov (%rbx),%rax <===== Code; ffffffffa0000619 <[jbd]journal_start+39/f0> 3: 48 39 38 cmp %rdi,(%rax) Code; ffffffffa000061c <[jbd]journal_start+3c/f0> 6: 74 34 je 3c <_RIP+0x3c> ffffffffa0000652 <[jbd]journal_start+72/f0> Code; ffffffffa000061e <[jbd]journal_start+3e/f0> 8: 49 c7 c0 c0 a6 00 a0 mov $0xffffffffa000a6c0,%r8 Code; ffffffffa0000625 <[jbd]journal_start+45/f0> f: b9 fa 00 00 00 mov $0xfa,%ecx
1 warning and 1 error issued. Results may not be reliable.
Thanks, Satya _________________________________________________________________ Pay Cash on delivery on lakhs of products. http://go.msnserver.com/IN/50757.asp Only on Baazee.com
"adelphia user" <sendtoadelphia@hotmail.com> writes:
Hello ,
I am seeing oopses in ext3 and also in reiserfs because of invalid current->journal_info. I am facing this problem in kernel 2.4.21-143-numa. This is on suse 8.1 amd64.
Try the latest kernel that is available for 9.0. Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Mon, Jun 21, 2004 at 09:07:40AM +0530, adelphia user wrote:
Hello ,
I am seeing oopses in ext3 and also in reiserfs because of invalid current->journal_info. I am facing this problem in kernel 2.4.21-143-numa. This is on suse 8.1 amd64.
This is very likely a kernel stack overflow. Do you use any special kernel modules? Please send your lsmod output. -Andi
participants (3)
-
adelphia user
-
Andi Kleen
-
Andreas Jaeger