linux-kernel - Re: [PATCH] security: do not check mmap_min

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: <20091203115858.d91b64dc.akpm@linux-foundation.org>
Date:	Thu, 3 Dec 2009 11:58:58 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Eric Paris <eparis@...hat.com>
Cc:	linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	uclinux-dist-devel@...ckfin.uclinux.org, dhowells@...hat.com,
	gyang@...ckfin.uclinux.org, john.johansen@...onical.com,
	Mike Frysinger <vapier.adi@...il.com>, stable@...nel.org
Subject: Re: [PATCH] security: do not check mmap_min_addr on nommu systems

On Thu, 03 Dec 2009 14:43:01 -0500
Eric Paris <eparis@...hat.com> wrote:

> nommu systems can do anything with memory they please and so they already
> win.  mmap_min_addr is the least of their worries.  Currently the
> mmap_min_addr implementation is problamatic on such systems.  This patch
> changes the addr_only argument to be a flags which can take the arguments
> for addr_only or not_addr.  LSMs then need to properly implement these two
> flags.

This replaces David's
nommu-ignore-the-address-parameter-in-the-file_mmap-security-check.patch,
which missed 2.6.32.

What are our thoughts wrt backporting this fix in some form into
2.6.32.x and earlier?


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