linux-kernel - Re: [PATCH mm] Remove deprecation of a.out ELF interpreters

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:	Thu, 31 Jan 2008 04:09:19 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH mm] Remove deprecation of a.out ELF interpreters

On Wed, Jan 30, 2008 at 03:29:15PM -0800, Andrew Morton wrote:
> On Wed, 30 Jan 2008 09:40:41 +0100
> Andi Kleen <andi@...stfloor.org> wrote:
> 
> > 
> > Andrew has already queued the patch to remove the support for a.out
> > ELF interpreters. So remove the deprecation with it too.
> > 
> 
> I'm trying to find which patch I might have queued which did this and came
> up blank. 

Sorry I somehow thought you had it queued.

My patch makes parts of David's patch obsolete because he makes 
the code ifdef, but I remove the code completely. David also
does some other cleanups which still make sense. 

So I think the correct way is to apply my patch first and then David's
and just ignore all the rejects and refresh.  The result should be correct.

Basically after that only the core dump changes in David's patch should
be left over.

Can you do that or should I resubmit both patches in a merged form?
(I can do that too) 

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