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: <20080914132742.GB554@elte.hu>
Date:	Sun, 14 Sep 2008 15:27:42 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>
Cc:	arjan@...ux.intel.com, tglx@...utronix.de, hpa@...or.com,
	andi@...stfloor.org, linux-kernel@...r.kernel.org,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Frans Pop <elendil@...net.nl>
Subject: Re: [patch 2/2] x86: Handle error returns in set_memory_*


* Venkatesh Pallipadi <venkatesh.pallipadi@...el.com> wrote:

> Correctly handle the error returns from set_memory_*. We have to free 
> memtype on error return path.

ah, so this is what caused the display artifacts reported by Frans Pop?

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