From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755523AbYGMWUT (ORCPT ); Sun, 13 Jul 2008 18:20:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754011AbYGMWUH (ORCPT ); Sun, 13 Jul 2008 18:20:07 -0400 Received: from rv-out-0506.google.com ([209.85.198.234]:57209 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753745AbYGMWUG (ORCPT ); Sun, 13 Jul 2008 18:20:06 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=JMs0S671QSY10pwUS8418QhQPta9fI951cpYtLRaoYMRtBQ1Q1fM0ngfZDansIPAyT h2IJH5HcH9d8WSSlGtt1+LF+esC3JSfOWHGVtsvkMjKe5IQy4GugAVo3i8mOcJEVVC5/ CQd3LdA9CsUjbCsvsCRRQ0Id+CkO4xkA7mIdU= Message-ID: <86802c440807131520g56cf1327g99eab24afbc6da06@mail.gmail.com> Date: Sun, 13 Jul 2008 15:20:05 -0700 From: "Yinghai Lu" To: "Ingo Molnar" Subject: Re: per-cpu related? Cc: "Vegard Nossum" , LKML , "Mike Travis" , "Thomas Gleixner" , "Steven Rostedt" In-Reply-To: <20080713210413.GB12362@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <86802c440807130116u3b850485jec220bc15892873e@mail.gmail.com> <19f34abd0807130455w516d73cfi80161c345564464@mail.gmail.com> <86802c440807131134i351f967dh3a2b94d687c767ee@mail.gmail.com> <20080713185502.GA17644@elte.hu> <86802c440807131401o21d016d0i37e6e4f9cad6bc2@mail.gmail.com> <20080713210413.GB12362@elte.hu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jul 13, 2008 at 2:04 PM, Ingo Molnar wrote: > > * Yinghai Lu wrote: > >> On Sun, Jul 13, 2008 at 11:55 AM, Ingo Molnar wrote: >> > >> > * Yinghai Lu wrote: >> > >> >> thanks >> >> >> >> could be caused by max_low_pfn_mapped patch...because hpet still use >> >> fixmap address that is cleared by others. >> >> still got >> >> calling __stack_chk_test+0x0/0x89 >> Testing -fstack-protector-all feature >> -fstack-protector-all test failed >> ------------[ cut here ]------------ >> WARNING: at kernel/panic.c:393 __stack_chk_test+0x61/0x89() >> Modules linked in: >> Pid: 1, comm: swapper Not tainted 2.6.26-rc9-tip-01873-ga9827e7-dirty #359 >> >> Call Trace: >> [] warn_on_slowpath+0x6c/0xa7 >> [] ? __stack_chk_test+0x0/0x89 >> [] ? __stack_chk_test+0x0/0x89 >> [] ? mcount_call+0x5/0x31 >> [] ? __stack_chk_test+0x0/0x89 >> [] __stack_chk_test+0x61/0x89 >> [] kernel_init+0x1de/0x346 >> [] ? mcount_call+0x5/0x31 >> [] ? finish_task_switch+0x14/0xe3 >> [] child_rip+0xa/0x11 >> [] ? kernel_init+0x0/0x346 >> [] ? child_rip+0x0/0x11 >> >> ---[ end trace 0f276ea63a4e83de ]--- > > please try latest tip/master - the self-test had to be removed. (gcc > will treat the stackprotector-failure function as ((noreturn)) attribute > and will optimize out the return path, making a reliable self-test > impossible in the way we tried to) > ok, you fixed it... that warning is gone. YH