linux-kernel - Re: [PATCH 05/05] x86: Rename paravirtualized TSC functions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Jul 2008 01:11:29 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	akataria@...are.com, "Thomas Gleixner" <tglx@...utronix.de>,
	"the arch/x86 maintainers" <x86@...nel.org>,
	"Daniel Hecht" <dhecht@...are.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"Jeremy Fitzhardinge" <jeremy@...p.org>
Subject: Re: [PATCH 05/05] x86: Rename paravirtualized TSC functions

On Thu, Jul 10, 2008 at 1:04 AM, Yinghai Lu <yhlu.kernel@...il.com> wrote:
> On Thu, Jul 10, 2008 at 12:50 AM, Ingo Molnar <mingo@...e.hu> wrote:
>>
>> * Yinghai Lu <yhlu.kernel@...il.com> wrote:
>>
>>> > that would be the tip/xen64 stuff, right? Does this revert:
>>> >
>>> > |    Revert "x86_64: there's no need to preallocate level1_fixmap_pgt"
>>> > |
>>> > |    This reverts commit 033786969d1d1b5af12a32a19d3a760314d05329.
>>> > |
>>> > |    Suresh Siddha reported that this broke booting on his 2GB testbox.
>>> >
>>> > solve your problems, or are there other problems still?
>>>
>>> still is bisecting it now...
>>
>> ok. I have no mystery crash on my test-systems.
>>
>> by the looks of it, your crashes seem to be pagetable related. If it's
>> in the tip/xen-64bit branch, my candidates would be:
>>
>>  0f38c08: x86: use __page_aligned_data/bss
>>  0337869: x86_64: there's no need to preallocate level1_fixmap_pgt
>>  89d7bb5: x86_64: add workaround for no %gs-based percpu
>>
>> 0337869 is reverted already.
>>
>> Or if it's an older commit, two candidates would be:
>>
>>  b50efd2: x86: introduce page_size_mask for 64bit
>>  3a9e189: x86: map UV chipset space - pagetable
>>
>> do you know the sha1 of the first broken tree? We know that
>> tip-history-2008-07-08_16.08_Tue is known-good.
>
> first round bisect all works..
>
> it seems make oldconfig change setting between different setting...
>
> diff .config config.full.good
> 4c4
> < # Thu Jul 10 00:52:52 2008
> ---
>> # Thu Jul 10 00:40:03 2008
> 295,296c295
> < CONFIG_CC_STACKPROTECTOR_ALL=y
> < CONFIG_CC_STACKPROTECTOR=y
> ---
>> # CONFIG_CC_STACKPROTECTOR is not set
>
> it seems some recent change doesn't like stackprotector.

reeing unused kernel memory: 996k freed
INIT: version 2.86 booting
init[1]: segfault at 28 ip ffffffffff600108 sp 00007fff71647a40 error 4
init[1]: segfault at 28 ip ffffffffff600108 sp 00007fff71646fc0 error 4
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.26-rc9-tip-01539-g7ef7459 #280

Call Trace:
 [<ffffffff80268672>] ? do_exit+0x84/0x6ce
 [<ffffffff80268d42>] ? do_group_exit+0x86/0xb3
 [<ffffffff802745b8>] ? get_signal_to_deliver+0x309/0x33d
 [<ffffffff80272877>] ? send_signal+0x23b/0x26e
 [<ffffffff802297e8>] ? do_notify_resume+0xd3/0x8fd
 [<ffffffff802c292b>] ? print_vma_addr+0x110/0x12f
 [<ffffffff80a4f3af>] ? do_page_fault+0x8ac/0x8fe
 [<ffffffff8022a4f4>] ? mcount_call+0x5/0x31
 [<ffffffff8022a4f4>] ? mcount_call+0x5/0x31
 [<ffffffff80270d34>] ? sigprocmask+0xbe/0xf6
 [<ffffffff8022ac78>] ? retint_signal+0x3d/0x85
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/