Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755405Ab1DNQkA (ORCPT ); Thu, 14 Apr 2011 12:40:00 -0400 Received: from mail-px0-f179.google.com ([209.85.212.179]:48961 "EHLO mail-px0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753448Ab1DNQj7 convert rfc822-to-8bit (ORCPT ); Thu, 14 Apr 2011 12:39:59 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 14 Apr 2011 18:39:58 +0200 Message-ID: Subject: Re: Kernel panic (NULL ptr deref?) in find_ge_pid()/next_pidmap() (via sys_getdents or sys_readdir) From: =?UTF-8?B?Um9iZXJ0IMWad2nEmWNraQ==?= To: linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 5552 Lines: 109 On Wed, Apr 13, 2011 at 11:36 PM, Robert Święcki wrote: > On Wed, Apr 13, 2011 at 11:12 PM, Robert Święcki wrote: >> Oops: (kdb's dumpall attached) >> >> [18608.476700] general protection fault: 0000 [#1] PREEMPT SMP >> [18608.476704] last sysfs file: >> /sys/devices/platform/microcode/power/runtime_status >> [18608.477002] CPU 0 >> [18608.477002] Pid: 31157, comm: iknowthis Not tainted 2.6.39-rc3 #4 >> Dell Inc. Precision WorkStation 390 /0GH911 >> [18608.477002] RIP: 0010:[] [] >> next_pidmap+0x38/0x7f >> [18608.477002] RSP: 0000:ffff88007b40fd48 EFLAGS: 00010203 >> [18608.477002] RAX: 0000000000000000 RBX: 001fffff82753988 RCX: 0000000000000034 >> [18608.477002] RDX: 0000000000003b6e RSI: 001ffffffff2c980 RDI: ffffffff82827000 >> [18608.477002] RBP: ffff88007b40fd68 R08: a000000000000000 R09: 5b68000000000000 >> [18608.477002] R10: ffff88007b40e000 R11: ffff88007b40fdb8 R12: ffffffff82827000 >> [18608.477002] R13: ffffffff82827808 R14: ffffffff81199146 R15: ffffffff81199146 >> [18608.477002] FS: 0000000000000000(0000) GS:ffff88012bc00000(0063) >> knlGS:00000000f75406c0 >> [18608.477002] CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b >> [18608.477002] CR2: 000000000809601c CR3: 0000000118457000 CR4: 00000000000006f0 >> [18608.477002] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 >> [18608.477002] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 >> [18608.477002] Process iknowthis (pid: 31157, threadinfo >> ffff88007b40e000, task ffff880124f6c560) >> [18608.477002] Stack: >> [18608.477002] ffff88011e2e5c80 00000000964c3b6d 0000000000000000 >> ffffffff82827000 >> [18608.477002] ffff88007b40fd98 ffffffff810ac446 ffff88011e2e5c80 >> ffffffff82827000 >> [18608.477002] 00000000964c3b6d ffff880124f68000 ffff88007b40fdf8 >> ffffffff811aedbb >> [18608.477002] Call Trace: >> [18608.477002] [] find_ge_pid+0x33/0x45 >> [18608.477002] [] next_tgid+0x3c/0x93 >> [18608.477002] [] ? compat_sys_io_getevents+0xae/0xae >> [18608.477002] [] ? get_pid_task+0x49/0x51 >> [18608.477002] [] proc_pid_readdir+0x15d/0x1b0 >> [18608.477002] [] ? compat_sys_io_getevents+0xae/0xae >> [18608.477002] [] ? compat_sys_io_getevents+0xae/0xae >> [18608.477002] [] ? compat_sys_io_getevents+0xae/0xae >> [18608.477002] [] proc_root_readdir+0x43/0x4b >> [18608.477002] [] vfs_readdir+0x71/0xae >> [18608.477002] [] compat_sys_getdents+0x81/0xcc >> [18608.477002] [] ia32_do_call+0x13/0x13 >> [18608.477002] Code: 0f 1f 44 00 00 ff c6 49 89 fc 89 f2 4c 8d af 08 >> 08 00 00 48 63 f6 81 e2 ff 7f 00 00 48 c1 ee 0f 48 c1 e6 04 48 8d 5c >> 37 08 eb 36 >> [18608.477002] 8b 7b 08 48 85 ff 74 27 48 63 d2 be 00 80 00 00 e8 66 ab 3e >> [18608.477002] RIP [] next_pidmap+0x38/0x7f >> [18608.477002] RSP >> [18626.313012] ---[ end trace 947a53151707da51 ]--- >> >> $ ./decodecode > Code: 0f 1f 44 00 00 ff c6 49 89 fc 89 f2 4c 8d af 08 08 00 00 48 63 >> f6 81 e2 ff 7f 00 00 48 c1 ee 0f 48 c1 e6 04 48 8d 5c 37 08 eb 36 >> >> Code starting with the faulting instruction >> =========================================== >> 0: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1) >> 5: ff c6 inc %esi >> 7: 49 89 fc mov %rdi,%r12 >> a: 89 f2 mov %esi,%edx >> c: 4c 8d af 08 08 00 00 lea 0x808(%rdi),%r13 >> 13: 48 63 f6 movslq %esi,%rsi >> 16: 81 e2 ff 7f 00 00 and $0x7fff,%edx >> 1c: 48 c1 ee 0f shr $0xf,%rsi >> 20: 48 c1 e6 04 shl $0x4,%rsi >> 24: 48 8d 5c 37 08 lea 0x8(%rdi,%rsi,1),%rbx >> 29: eb 36 jmp 0x61 I'm surprised by the discrepancy between this oops, and kdb memory dump: >From oops/kdb (from address 0xffffffff810ac3a1 which is start of next_pidmap) Code: 0f 1f 44 00 00 ff c6 49 89 fc 89 f2 4c 8d af 08 08 00 00 48.... >From objdump vmlinux (the same address) Code: e8 1a 88 e7 00 ff c6 49 89 fc 89 f2 4c 8d af 08 08 00 00 48... Which decodes to kdb: 0: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1) 5: ff c6 inc %esi 7: 49 89 fc mov %rdi,%r12 a: 89 f2 mov %esi,%edx c: 4c 8d af 08 08 00 00 lea 0x808(%rdi),%r13 vmlinux: ffffffff810ac3a1: e8 1a 88 e7 00 callq ffffffff81f24bc0 ffffffff810ac3a6: ff c6 inc %esi ffffffff810ac3a8: 49 89 fc mov %rdi,%r12 ffffffff810ac3ab: 89 f2 mov %esi,%edx ffffffff810ac3ad: 4c 8d af 08 08 00 00 lea 0x808(%rdi),%r13 Might this difference (nopl 0x0(%rax,%rax,1) vs callq ffffffff81f24bc0 at 0xffffffff810ac3a1) be some kind of kernel instrumentation (ftrace, perf or so), or a symptom of a bug (overwritten memory)? -- Robert Święcki -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/