[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAE9FiQVTTei2RnuCzNMvSXkkfT6XROfFpG2LZqDeFYRcUwUv6A@mail.gmail.com>
Date: Mon, 16 Mar 2015 12:25:41 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Kees Cook <keescook@...omium.org>,
Borislav Petkov <bp@...e.de>, Baoquan He <bhe@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Jiri Kosina <jkosina@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Matt Fleming <matt.fleming@...el.com>
Subject: Re: [PATCH v4] x86, boot: Make data from decompress_kernel stage live longer
On Mon, Mar 16, 2015 at 12:45 AM, Ingo Molnar <mingo@...nel.org> wrote:
>
> * Yinghai Lu <yinghai@...nel.org> wrote:
>
>> After commit f47233c2d34f ("x86/mm/ASLR: Propagate base load address
>> calculation"), get warning about setup_data from debugfs for
>> setup_data. Boris found setup_data for kaslr from boot stage become
>> all 0's in kernel stage.
>
> And? What is the high level effect to the user?
>
> 'setup_data for kaslr from boot stage becomes all 0's' is not a high
> level effect. It's a detail of the mechanism of the bug, not a high
> level effect.
>
> Think of a regular Linux user reading your changelogs. The first
> paragraph of bug fixes should be readable to them!
That should be ioremap warning that reported by
http://marc.info/?l=linux-kernel&m=142492905425130&w=2
and later Boris found those all 0's.
Thanks
Yinghai
--
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/
Powered by blists - more mailing lists