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
| ||
|
Date: Mon, 29 Oct 2012 19:00:38 +0800 From: Wen Congyang <wency@...fujitsu.com> To: richard -rw- weinberger <richard.weinberger@...il.com> CC: x86@...nel.org, linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org, Rob Landley <rob@...dley.net>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, bhelgaas@...gle.com, "H. Peter Anvin" <hpa@...or.com>, Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [PATCH v3 1/2] update mem= option's spec according to its implementation At 10/29/2012 06:48 PM, richard -rw- weinberger Wrote: > On Mon, Oct 29, 2012 at 9:48 AM, Wen Congyang <wency@...fujitsu.com> wrote: >> Current mem= implementation seems buggy because specification and >> implementation doesn't match. Current mem= has been working >> for many years and it's not buggy, it works as expected. So >> we should update the specification. >> >> Signed-off-by: Wen Congyang <wency@...fujitsu.com> >> Sort-of-tentatively-acked-by: Rob Landley <rob@...dley.net> > > So, is this an ACK or not? > I don't know. Here is the origin message: At 06/15/2012 04:22 AM, Rob Landley Wrote: > I have no objection to this but can't confirm it's true or not without > an awful lot more digging through the code I don't have time for right > now. (All the x86-32 machines I've used just had the 640k->1m hole and > the rest was contiguous memory, so the behavior would be the same either > way...) > > Sort-of-tentatively-acked-by: Rob Landley <rob@...dley.net> > > Rob -- 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