linux-kernel - Impact of removing VM

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

Message-ID: <20141113122406.GA19763@linux-mips.org>
Date:	Thu, 13 Nov 2014 13:24:06 +0100
From:	Ralf Baechle <ralf@...ux-mips.org>
To:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	linux-mips@...ux-mips.org, libc-alpha@...rceware.org
Subject: Impact of removing VM_EXEC from brk area

A patch to remove VM_EXEC from VM_DATA_DEFAULT_FLAGS for MIPS has been
submitted to me with the primary motivation for this change being
some performance improvment.  In other words, the patch would remove
execute permission from a process brk area.  It's however unclear to
me how much software wreckage would result from such a change, even
if the execute permission for the stack area remains unchanged.

So, what would break?

Thanks,

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