linux-kernel - Re: [PATCH 06/19] x86, mpx: we do not allocate the bounds directory

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:	Mon, 18 May 2015 22:43:29 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Dave Hansen <dave@...1.net>
cc:	linux-kernel@...r.kernel.org, x86@...nel.org,
	dave.hansen@...ux.intel.com
Subject: Re: [PATCH 06/19] x86, mpx: we do not allocate the bounds
 directory

On Fri, 8 May 2015, Dave Hansen wrote:

> Subject: x86, mpx: we do not allocate the bounds directory

led me to expect, that we actually do something like this.

  x86, mpx: Restrict mmap size check to bounds tables

might be more accurate.

> 
> From: Dave Hansen <dave.hansen@...ux.intel.com>
> 
> The comment and code here are confusing.  We do not currently
> allocate the bounds directory in the kernel.
> 
> Signed-off-by: Dave Hansen <dave.hansen@...ux.intel.com>

Otherwise

Reviewed-by: Thomas Gleixner <tglx@...utronix.de>
--
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/