linux-kernel - Re: [PATCH v7u1 10/31] x86, 64bit: Don't set max_pfn

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 11 Jan 2013 08:42:05 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Borislav Petkov <bp@...en8.de>, Yinghai Lu <yinghai@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jan Kiszka <jan.kiszka@....de>,
	Jason Wessel <jason.wessel@...driver.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7u1 10/31] x86, 64bit: Don't set max_pfn_mapped wrong
 value early on native path

On Fri, Jan 11, 2013 at 4:13 AM, Borislav Petkov <bp@...en8.de> wrote:
> On Thu, Jan 03, 2013 at 04:48:30PM -0800, Yinghai Lu wrote:
>> We are not having max_pfn_mapped set correctly until init_memory_mapping.
>>
>> so don't print it initial value for 64bit
>
> Just a minor nitpick:
>
> "So don't print its initial value for 64bit."

OK.

>
> And you don't need the newlines between each sentence.

Just want to make it more readable.

>
> Acked-by: Borislav Petkov <bp@...e.de>

Thanks, I add that.

Also, congratulation for the new job.

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/