mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Andy Whitcroft <apw@shadowen.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [BUG] linux-next: Tree for April 9 warning on CC_STACKPROTECTOR, followed by kernel panic
Date: Thu, 10 Apr 2008 21:47:11 +1000	[thread overview]
Message-ID: <20080410214711.cf0c57c7.sfr@canb.auug.org.au> (raw)
In-Reply-To: <47FDE045.4070509@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 4376 bytes --]

CC to Ingo ...

On Thu, 10 Apr 2008 15:09:17 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
>
> Hi Stephen,
> 
> The next-20080409 kernel warns while booting up on a x86_64 machine.
> When compiled the kernel with CONFIG_CC_STACKPROTECTOR=y, the warning
> is followed by the kernel panic.
> 
> Testing -fstack-protector-all feature
> No -fstack-protector-stack-frame!
> -fstack-protector-all test failed
> ------------[ cut here ]------------
> WARNING: at kernel/panic.c:365 __stack_chk_test+0x4b/0x50()
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.25-rc8-next-20080409-autotest #1
> 
> Call Trace:
>  [<ffffffff80231f5e>] warn_on_slowpath+0x51/0x63
>  [<ffffffff80232d93>] printk+0x4e/0x56
>  [<ffffffff80382fcd>] extract_entropy+0x47/0x90
>  [<ffffffff80230000>] dup_mm+0xca/0x3fd
>  [<ffffffff80231eba>] __stack_chk_test_func+0x21/0x32
>  [<ffffffff80231fbb>] __stack_chk_test+0x4b/0x50
>  [<ffffffff808ba8f1>] kernel_init+0x189/0x2f9
>  [<ffffffff804ee221>] _spin_unlock_irq+0x9/0xc
>  [<ffffffff8020cb88>] child_rip+0xa/0x12
>  [<ffffffff808ba768>] kernel_init+0x0/0x2f9
>  [<ffffffff8020cb7e>] child_rip+0x0/0x12
> 
> ---[ end trace d88d2f3a71e3b32c ]---
> Freeing unused kernel memory: 368k freed
> Write protecting the kernel read-only data: 4188k
> BUG: unable to handle kernel NULL pointer dereference at 00000000000002e8
> IP: [<ffffffff80286c11>] kmem_cache_alloc+0x19/0x6b
> PGD 3e925067 PUD 3e924067 PMD 0 
> Oops: 0000 [1] SMP 
> last sysfs file: 
> CPU 0 
> Modules linked in:
> Pid: 1, comm: init Not tainted 2.6.25-rc8-next-20080409-autotest #1
> RIP: 0010:[<ffffffff80286c11>]  [<ffffffff80286c11>] kmem_cache_alloc+0x19/0x6b
> RSP: 0000:ffff81003f9c9f08  EFLAGS: 00010046
> RAX: 0000000000000000 RBX: 0000000000000246 RCX: ffffffff80211f7e
> RDX: 00007fff1f89e710 RSI: 00000000000000d0 RDI: 0000000000000000
> RBP: 00007fff1f89e6f8 R08: 000000000065e300 R09: 000000000065e2e8
> R10: 000000000066d800 R11: 0000000000000203 R12: 00000000000000d0
> R13: 000000000047c290 R14: 000000000047c250 R15: 0000000000000000
> FS:  000000000066d870(0063) GS:ffffffff8067a000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 00000000000002e8 CR3: 000000003e921000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process init (pid: 1, threadinfo ffff81003f9c8000, task ffff81003f9c6000)
> Stack:  ffff81003f9c6000 00007fff1f89e6f8 0000000000000002 ffffffff80211f7e
>  ffff81003e920060 ffffffff8033419c ffff81003f9c6000 ffffffff8020d96a
>  0000000000000000 ffffffff804ee379 0000000000000000 000000000047c250
> Call Trace:
>  [<ffffffff80211f7e>] ? init_fpu+0x88/0xc9
>  [<ffffffff8033419c>] ? __up_read+0x13/0x8a
>  [<ffffffff8020d96a>] ? math_state_restore+0x19/0x5a
>  [<ffffffff804ee379>] ? error_exit+0x0/0x51
> 
> 
> Code: 4b 18 31 c0 48 89 f7 fc f3 aa 5b 5d 41 5c 48 89 f0 c3 41 54 41 89 f4 55 53 48 8b 4c 24 18 9c 5b fa 65 8b 04 25 24 00 00 00 48 98 <48> 8b ac c7 e8 02 00 00 48 8b 55 00 48 85 d2 75 10 83 ca ff 49 
> RIP  [<ffffffff80286c11>] kmem_cache_alloc+0x19/0x6b
>  RSP <ffff81003f9c9f08>
> CR2: 00000000000002e8
> ---[ end trace d88d2f3a71e3b32c ]---
> Kernel panic - not syncing: Attempted to kill init!
> Pid: 1, comm: init Tainted: G      D  2.6.25-rc8-next-20080409-autotest #1
> 
> Call Trace:
>  [<ffffffff8023225d>] panic+0x86/0x144
>  [<ffffffff80251911>] kallsyms_lookup+0x49/0x80
>  [<ffffffff80286c11>] kmem_cache_alloc+0x19/0x6b
>  [<ffffffff80232d93>] printk+0x4e/0x56
>  [<ffffffff80232d93>] printk+0x4e/0x56
>  [<ffffffff802351c9>] do_exit+0x71/0x682
>  [<ffffffff804ee731>] oops_begin+0x0/0x8c
>  [<ffffffff804f058d>] do_page_fault+0x738/0x7f3
>  [<ffffffff804ee379>] error_exit+0x0/0x51
>  [<ffffffff80211f7e>] init_fpu+0x88/0xc9
>  [<ffffffff80286c11>] kmem_cache_alloc+0x19/0x6b
>  [<ffffffff80211f7e>] init_fpu+0x88/0xc9
>  [<ffffffff8033419c>] __up_read+0x13/0x8a
>  [<ffffffff8020d96a>] math_state_restore+0x19/0x5a
>  [<ffffffff804ee379>] error_exit+0x0/0x51
> 
> -- 
> Thanks & Regards,
> Kamalesh Babulal,
> Linux Technology Center,
> IBM, ISTL.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-04-10 11:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  8:53 linux-next: Tree for April 9 Stephen Rothwell
     [not found] ` <d711229d0804090400p1c92a158j381b86e207a6f38a@mail.gmail.com>
2008-04-09 11:09   ` Stephen Rothwell
2008-04-09 11:27     ` Stephen Rothwell
2008-04-09 11:26       ` Jacek Luczak
2008-04-09 11:34         ` Ingo Molnar
2008-04-09 11:55           ` Jacek Luczak
2008-04-09 12:01           ` Ingo Molnar
2008-04-09 11:31       ` Ingo Molnar
2008-04-09 14:50         ` Cyrill Gorcunov
2008-04-09 15:03           ` Ingo Molnar
2008-04-09 15:18             ` Cyrill Gorcunov
2008-04-09 16:55 ` Stefan Richter
2008-04-10  0:45   ` Stephen Rothwell
2008-04-10  6:52   ` Ingo Molnar
2008-04-10  7:44     ` Stephen Rothwell
2008-04-10  7:52       ` debug Kconfig option (was Re: linux-next: Tree for April 9) Stefan Richter
2008-04-10  9:51         ` Ingo Molnar
2008-04-10 19:05           ` [PATCH linux1394-2.6.git] firewire: fw-ohci: add option for remote debugging - amendment Stefan Richter
2008-04-10 22:08             ` Stefan Richter
2008-04-10 15:01         ` debug Kconfig option (was Re: linux-next: Tree for April 9) Randy Dunlap
2008-04-10  9:48       ` linux-next: Tree for April 9 Ingo Molnar
2008-04-10 19:02         ` Stefan Richter
2008-04-10  9:39 ` [BUG] linux-next: Tree for April 9 warning on CC_STACKPROTECTOR, followed by kernel panic Kamalesh Babulal
2008-04-10 10:14   ` Jacek Luczak
2008-04-10 10:51     ` Kamalesh Babulal
2008-04-10 10:58       ` Jacek Luczak
2008-04-10 11:47   ` Stephen Rothwell [this message]
2008-04-11  9:45     ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080410214711.cf0c57c7.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=apw@shadowen.org \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®