linux-kernel - Re: [PATCH] New PT_GNU_COMPAT segment header extension

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: <b544312a-6cd1-475d-b719-c3d1cbe6fc3f@zmail15.collab.prod.int.phx2.redhat.com>
Date:	Mon, 06 Feb 2012 07:08:30 -0500 (EST)
From:	Ramon de C Valle <rcvalle@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] New PT_GNU_COMPAT segment header extension

Hi Andrew,

> <I have been poked>
> 
> I saw the patch but it's one of those ones which looks tricky/risky,
> and is in an area with which I'm not sufficiently familiar.  I used
> to
> ask Roland McGrath to help out with this sort of thing, but he
> dematerialised a while back.  Perhaps Linus can give it some thought?
> I'd suggest a resend: you've added useful info in later emails so
> there
> would be benefit to bringing it all together in one place.
> 
> A couple of minor things:
> 
> - The patch will need a Signed-off-by:, as described in
>   Documentation/SubmittingPatches.

Sure. I'm going to resend the patches properly formatted with all
information together.

> 
> - The term "compat" has a well-understood meaning in the kernel: it
>   refers to the support of 32-bit executables under 64-bit kernels.
>   Adding an unrelated PT_GNU_COMPAT muddies this.  Can you think up a
>   different term?

I previously thought about using PT_GNU_LEGACY. Sounds reasonable?

> 
> 
> 

-- 
Ramon de C Valle / Red Hat Security Response Team
--
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/