linux-kernel - Re: [patch 2/2] x86: Handle error returns in set_memory

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: <20080930212949.GL15609@linux-os.sc.intel.com>
Date:	Tue, 30 Sep 2008 14:29:50 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	Frans Pop <elendil@...net.nl>
Cc:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	Ingo Molnar <mingo@...e.hu>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"hpa@...or.com" <hpa@...or.com>,
	"andi@...stfloor.org" <andi@...stfloor.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>
Subject: Re: [patch 2/2] x86: Handle error returns in set_memory_*

On Tue, Sep 30, 2008 at 01:36:04AM -0700, Frans Pop wrote:
> As I mentioned before, I only tested with the first of the two patches
> (as you asked me to) and that solved the artifacts for me. What's the
> explanation behind that?
> 
> What is the relationship between the first and second patch?

Frans, There is no relationship between the two patches. First patch
(track memtype for RAM in page struct) will fix the behavior you
observed and the second patch addresses some error conditions which
were noticed by Venki.

Both should have been pushed independently.

thanks,
suresh
--
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/