linux-kernel - Re: [PATCH] FDPIC: Ignore the loader's PT_GNU

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:	Wed, 08 Jul 2009 12:01:40 +0100
From:	David Howells <dhowells@...hat.com>
To:	Pavel Machek <pavel@....cz>
Cc:	dhowells@...hat.com, vapier.adi@...il.com,
	rgetz@...ckfin.uclinux.org, lethal@...ux-sh.org, gerg@...inux.org,
	uclinux-dist-devel@...ckfin.uclinux.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] FDPIC: Ignore the loader's PT_GNU_STACK when calculating the stack size

Pavel Machek <pavel@....cz> wrote:

> The patch seems wrong to me; loader needs the stack, too, right?
> 
> What about making sure that the loader specifies reasonable stack
> size, instead?

The loader doesn't need its own stack, unless it _is_ the executable.  It uses
the executable's stack.  The problem is that the executable and the loader can
both specify the stack size for NOMMU, but which one do we pick, or do we
consider both.

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