linux-kernel - Re: CPU MTRRs and linux kernel

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:	Tue, 12 Jun 2012 08:17:43 -0700 (PDT)
From:	Mahmood Naderan <nt_mahmood@...oo.com>
To:	Borislav Petkov <bp@...en8.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andreas Herrmann <andreas.herrmann3@....com>
Subject: Re: CPU MTRRs and linux kernel

>If it were me and I didn't have any particular reason to stick with
>2.6.32, I'd always go for the latest kernel
 
One thing is not clear for me. Did you make the following change in the latest version today? I want to know, should I wait until it is pushed in to ubuntu repository?

diff --git a/arch/x86/kernel/cpu/mtrr/cleanup.c b/arch/x86/kernel/cpu/mtrr/cleanup.c
index c5f59d071425..ac140c7be396 100644
--- a/arch/x86/kernel/cpu/mtrr/cleanup.c
+++ b/arch/x86/kernel/cpu/mtrr/cleanup.c
@@ -827,7 +827,7 @@ int __init amd_special_default_mtrr(void)

        if (boot_cpu_data.x86_vendor != X86_VENDOR_AMD)
                return 0;
-       if (boot_cpu_data.x86 < 0xf || boot_cpu_data.x86 > 0x11)
+       if (boot_cpu_data.x86 < 0xf)
                return 0;
        /* In case some hypervisor doesn't pass SYSCFG through: */
        if (rdmsr_safe(MSR_K8_SYSCFG, &l, &h) < 0)



// Naderan *Mahmood;


----- Original Message -----
From: Borislav Petkov <bp@...en8.de>
To: Mahmood Naderan <nt_mahmood@...oo.com>
Cc: LKML <linux-kernel@...r.kernel.org>; Andreas Herrmann <andreas.herrmann3@....com>
Sent: Tuesday, June 12, 2012 6:27 PM
Subject: Re: CPU MTRRs and linux kernel

On Tue, Jun 12, 2012 at 06:48:10AM -0700, Mahmood Naderan wrote:
> Thanks Borislav, I want to know, should I upgrade to the latest kernel
> or it is possible to download the source of 2.6.32-24 from repository
> and modify cleanup.c and then recompile?

Whatever you decide.

If it were me and I didn't have any particular reason to stick with
2.6.32, I'd always go for the latest kernel.

In any case, no matter which kernel you're installing, just make sure it
contains the aforementioned patch which should fix your problem.

HTH.

-- 
Regards/Gruss,
Boris.
--
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/

--
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/