From: Arnd Bergmann <arnd@arndb.de>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, tony.luck@intel.com,
ralf@linux-mips.org, kyle@mcmartin.ca, benh@kernel.crashing.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
davem@davemloft.net, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, viro@zeniv.linux.org.uk
Subject: Re: [PATCH 4/6] improve sys_personality for compat architectures
Date: Tue, 2 Feb 2010 15:36:51 +0100 [thread overview]
Message-ID: <201002021536.51928.arnd@arndb.de> (raw)
In-Reply-To: <20100201185607.GD11045@lst.de>
On Monday 01 February 2010, Christoph Hellwig wrote:
> +/*
> + * Get/set the personality.
> + *
> + * Note that we simply return PER_LINUX even if we actually have a 32-bit
> + * task (PER_LINUX32) as this is expected by 32-bit userland.
> + */
> SYSCALL_DEFINE1(personality, u_long, personality)
> {
> u_long old = current->personality;
>
> if (personality != 0xffffffff) {
> + if (personality(old) == PER_LINUX32 &&
> + personality == PER_LINUX)
> + personality = PER_LINUX32;
> set_personality(personality);
> if (current->personality != personality)
> return -EINVAL;
> }
>
> - return (long)old;
> + return (long)(old == PER_LINUX32 ? PER_LINUX : old);
> }
What does this do for a native 64 bit process setting PER_LINUX32?
It looks to me like it could never set it back to the original
value, or am I missing something here?
It's what the arch specific code does already, but it seems a bit
strange anyway.
Arnd
next prev parent reply other threads:[~2010-02-02 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 18:56 [PATCH 4/6] improve sys_personality for compat architectures Christoph Hellwig
2010-02-02 14:36 ` Arnd Bergmann [this message]
2010-02-02 16:31 ` Christoph Hellwig
2010-02-03 17:06 ` Arnd Bergmann
2010-02-03 17:13 ` David Miller
2010-02-03 20:04 ` H. Peter Anvin
2010-02-04 7:38 ` Arnd Bergmann
2010-02-04 16:00 ` Christoph Hellwig
2010-03-05 19:49 ` Andrew Morton
2010-03-09 12:58 ` Christoph Hellwig
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=201002021536.51928.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=kyle@mcmartin.ca \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.