linux-kernel - Re: [PATCH v2] x86, e820: panic on sanitizing invalid memory map

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] [day] [month] [year] [list]

Message-ID: <54472144.3090802@martingkelly.com>
Date:	Tue, 21 Oct 2014 20:15:16 -0700
From:	Martin Kelly <martin@...tingkelly.com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	linux-kernel@...r.kernel.org, x86@...nel.org, mingo@...hat.com,
	hpa@...or.com, akpm@...ux-foundation.org, rientjes@...gle.com,
	david.vrabel@...rix.com, Martin Kelly <martkell@...zon.com>
Subject: Re: [PATCH v2] x86, e820: panic on sanitizing invalid memory map

On 10/21/2014 12:44 PM, Thomas Gleixner wrote:
> On Tue, 21 Oct 2014, Martin Kelly wrote:
>> On 10/21/2014 01:56 AM, Thomas Gleixner wrote:
>> Thomas, do you see any issues with a revision that separates out the
>> return values (0 for a map with 1 entry, -1 for a map with invalid
>> entries) and adds checks in the callers, where appropriate?
> 
> I think that's a sane approach.
> 

Alright, I will work on a new patch doing that, separating out each call
site (and relevant error handling) into its own patch.
--
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/