From: Eric B Munson <ebmunson@us.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] Keep 3 high personality bytes across exec
Date: Mon, 30 Jun 2008 08:56:30 -0700 [thread overview]
Message-ID: <20080630155630.GA8445@us.ibm.com> (raw)
In-Reply-To: <18536.38684.384039.662264@cargo.ozlabs.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
On Mon, 30 Jun 2008, Paul Mackerras wrote:
> Eric B Munson writes:
>
> > --- a/include/asm-powerpc/elf.h
> > +++ b/include/asm-powerpc/elf.h
> > @@ -257,7 +257,8 @@ do { \
> > else \
> > clear_thread_flag(TIF_ABI_PENDING); \
> > if (personality(current->personality) != PER_LINUX32) \
> > - set_personality(PER_LINUX); \
> > + set_personality(PER_LINUX | \
> > + (current->personality & PER_INHERIT)); \
>
> Couldn't we use ~PER_MASK here instead of PER_INHERIT? That would
> mean we wouldn't have to modify include/linux/personality.h, and we
> wouldn't have to keep updating PER_INHERIT as more flags get added.
>
> (Nice patch description, BTW. Thanks.)
>
> Paul.
>
Yeah, ~PER_MASK will work fine. I used PER_INHERIT first because I
was not sure if there were values that should not be carried forward.
I will have an updated patch out shortly.
Eric
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-06-30 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 0:08 [PATCH V2] Keep 3 high personality bytes across exec Eric B Munson
2008-06-30 8:19 ` Paul Mackerras
2008-06-30 15:56 ` Eric B Munson [this message]
2008-06-30 16:12 ` [PATCH V3] " Eric Munson
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=20080630155630.GA8445@us.ibm.com \
--to=ebmunson@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).