linux-kernel - Re: [PATCH resend v3] x86: memtest: WARN if bad RAM found

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]

Message-ID: <CAE9FiQVSdnqrno4VBZbcQmcYagpXPOo_Cvw=c9w_1GZycKv1Xg@mail.gmail.com>
Date:	Mon, 23 Apr 2012 13:26:18 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Jonathan Nieder <jrnieder@...il.com>
Cc:	x86@...nel.org, Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Ben Hutchings <ben@...adent.org.uk>,
	Andreas Herrmann <andreas.herrmann3@....com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, Dave Jones <davej@...hat.com>
Subject: Re: [PATCH resend v3] x86: memtest: WARN if bad RAM found

On Mon, Apr 23, 2012 at 11:26 AM, Jonathan Nieder <jrnieder@...il.com> wrote:
>
>  arch/x86/mm/memtest.c |    2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/arch/x86/mm/memtest.c b/arch/x86/mm/memtest.c
> index c80b9fb95734..38caeb44a218 100644
> --- a/arch/x86/mm/memtest.c
> +++ b/arch/x86/mm/memtest.c
> @@ -30,6 +30,8 @@ static u64 patterns[] __initdata = {
>
>  static void __init reserve_bad_mem(u64 pattern, u64 start_bad, u64 end_bad)
>  {
> +       WARN_ONCE(1, "Bad RAM detected. Use memtest86+ to perform a thorough test\n"
> +                 "and the memmap= parameter to reserve the bad areas.");

You must be kidding : calling memtest86+ "thorough test".

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/