linux-kernel - RE: [PATCH] x86/pat: no need to check overlaps with more than one entry in chk

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: <7E82351C108FA840AB1866AC776AEC46767A389F@orsmsx505.amr.corp.intel.com>
Date:	Wed, 18 Nov 2009 09:30:58 -0800
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	Xiaotian Feng <dfeng@...hat.com>, "x86@...nel.org" <x86@...nel.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...hat.com>,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>
Subject: RE: [PATCH] x86/pat: no need to check overlaps with more than one
 entry in chk_conflict

>-----Original Message-----
>From: linux-kernel-owner@...r.kernel.org 
>[mailto:linux-kernel-owner@...r.kernel.org] On Behalf Of Xiaotian Feng
>Sent: Tuesday, November 17, 2009 6:48 PM
>To: x86@...nel.org
>Cc: linux-kernel@...r.kernel.org; Xiaotian Feng; Ingo Molnar; 
>Siddha, Suresh B; Pallipadi, Venkatesh
>Subject: [PATCH] x86/pat: no need to check overlaps with more 
>than one entry in chk_conflict
>
>memtype list is built via reserve_memtype, for the overlapped 
>areas, they're
>all the same type, otherwise reserve_memtype will fail to 
>insert it into the
>list. So there's no need to check overlaps with more than one 
>entry in the
>chk_conflict code.

NAK.

The reason we have to check for more than one entry is for the cases
like this.

New entry:                   s-------------------e
Existing entries:         s----e     s-----e   s----e
(s=start, e=end)

Thanks,
Venki--
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/