linux-kernel - Re: [PATCH] Add range_is_allowed() check to mmap of /dev/mem

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: <20080307083754.GD12150@elte.hu>
Date:	Fri, 7 Mar 2008 09:37:54 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Venki Pallipadi <venkatesh.pallipadi@...el.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>, arjan@...ux.intel.com,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Add range_is_allowed() check to mmap of /dev/mem


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

> Earlier patch that introduced CONFIG_NONPROMISC_DEVMEM, did the 
> range_is_allowed() check only for read and write. Add 
> range_is_allowed() check to mmap of /dev/mem as well.
> 
> Changes the paramaters of range_is_allowed() to pfn and size to handle 
> more than 32 bits of physical address on 32 bit arch cleanly.

thanks, applied.

	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/