linux-mips
[Top] [All Lists]

Re: Bug#380531: linux-2.6: mips and mipsel personality(2) support is bro

To: linux-mips@linux-mips.org
Subject: Re: Bug#380531: linux-2.6: mips and mipsel personality(2) support is broken
From: Martin Michlmayr <tbm@cyrius.com>
Date: Mon, 31 Jul 2006 00:41:37 +0200
Cc: Roger Leigh <rleigh@debian.org>, 380531-silent@bugs.debian.org
In-reply-to: <20060730183939.7119.48747.reportbug@hardknott.home.whinlatter.ukfsn.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20060730183939.7119.48747.reportbug@hardknott.home.whinlatter.ukfsn.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.11+cvs20060403
FYI, but report tht "mips and mipsel personality(2) support is broken"

* Roger Leigh <rleigh@debian.org> [2006-07-30 19:39]:
> personality(2) only works the first time it is called [in the lifetime
> of a process/program].  All subsequent calls return EPERM, which is
> not a documented return value; I can see no mention of it in
> kernel/execdomain.c.  None of the other architectures I have tested
> (amd64, arm, i386, ia64, powerpc) behave this way: personality(2) is
> not a privileged call.
> 
> This happens no matter what the value of persona is, even if it is
> just 0xffffffff to query the current personality.
> 
> The attached testcase demonstrates the breakage.  On a working
> platform (powerpc), the output is like this:
> 
> ------------------------
> $ ./testpersona
> Getting personality
> Get returned '0'
> Setting personality '8'
> Set OK
> Getting personality
> Get returned '8'
> Setting personality '0'
> Set OK
> Getting personality
> Get returned '0'
> ------------------------
> 
> 0 == PER_LINUX
> 8 == PER_LINUX32
> 
> It successfully switched from PER_LINUX to PER_LINUX32 and back again,
> checking the personality before and after each change.
> 
> 
> Regards,
> Roger

-- 
Martin Michlmayr
http://www.cyrius.com/

Attachment: testpersona.c
Description: Text Data

<Prev in Thread] Current Thread [Next in Thread>