linux-kernel - Re: [PATCH 1/4] FDPIC: Respect PT_GNU_STACK exec protection markings when creating NOMMU stack

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: <24434.1262258139@redhat.com>
Date:	Thu, 31 Dec 2009 11:15:39 +0000
From:	David Howells <dhowells@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	dhowells@...hat.com, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, uclinux-dev@...inux.org,
	Mike Frysinger <vapier@...too.org>
Subject: Re: [PATCH 1/4] FDPIC: Respect PT_GNU_STACK exec protection markings when creating NOMMU stack

Andrew Morton <akpm@...ux-foundation.org> wrote:

> So these patches and the MN10300 ones didn't get merged.  Presumably
> because they're a grabbag of fixes and non-fixes and kinda-fixes with
> no particular ordering or precedence and they arrived newly-minted
> several days after the release of -rc1.
> 
> I could suggest that you go back and sort them into 2.6.33-appropriate
> fixes and 2.6.34-appropriate non-fixes.
> 
> Or you could try to cook up a good-sounding reason why the whole lot
> needs to go into 2.6.33.  If you believe that ;)

I did send them, plus others, during the merge window (albeit near the end).

I then sent this lot after filtering out the extensions that should probably
wait for the next merge window.

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/