From: Ramon de C Valle <rcvalle@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] New PT_GNU_COMPAT segment header extension
Date: Mon, 06 Feb 2012 07:08:30 -0500 (EST) [thread overview]
Message-ID: <b544312a-6cd1-475d-b719-c3d1cbe6fc3f@zmail15.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <20120201141311.05b873ab.akpm@linux-foundation.org>
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
next prev parent reply other threads:[~2012-02-06 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ae010933-d93f-4858-97c7-d5aeb3dd73bc@zmail15.collab.prod.int.phx2.redhat.com>
2012-01-09 11:54 ` [PATCH] New PT_GNU_COMPAT segment header extension Ramon de C Valle
2012-02-01 22:13 ` Andrew Morton
2012-02-06 12:08 ` Ramon de C Valle [this message]
[not found] <90c73bcf-9c80-47c2-a0de-89bc066013d1@zmail15.collab.prod.int.phx2.redhat.com>
2012-01-13 13:56 ` Ramon de C Valle
2012-01-13 15:33 ` Ramon de C Valle
2012-01-13 16:03 ` Ramon de C Valle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b544312a-6cd1-475d-b719-c3d1cbe6fc3f@zmail15.collab.prod.int.phx2.redhat.com \
--to=rcvalle@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).