Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Carsten Langgaard <carstenl@mips.com>
Cc: "H. J. Lu" <hjl@lucon.org>, linux-mips@oss.sgi.com
Subject: Re: Personality
Date: Tue, 16 Jul 2002 12:36:32 +0200	[thread overview]
Message-ID: <20020716123632.B17038@dea.linux-mips.net> (raw)
In-Reply-To: <3D33DAB2.353A4399@mips.com>; from carstenl@mips.com on Tue, Jul 16, 2002 at 10:34:58AM +0200

On Tue, Jul 16, 2002 at 10:34:58AM +0200, Carsten Langgaard wrote:

> The include/linux/personality.h file has changed between the 2.4.3 and
> the 2.4.18 kernel.
> Now there is a define of personality (#define personality(pers) (pers &
> PER_MASK), but that breaks things for the users, if they include this
> file.
> The user wishes to call the glibc personality function (which do the
> syscall), and not use the above definition.
> 
> So I guess we need a "#ifdef __KERNEL__" around some of the code in
> include/linux/personality.h (at least around the define of personality),
> which then has to go into the glibc kernel header files.

The general policy about such problems is to not use kernel include files
from user applications directly.  Hjl - maybe time for <sys/personality.h>?

  Ralf

  reply	other threads:[~2002-07-16 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16  8:34 Personality Carsten Langgaard
2002-07-16 10:36 ` Ralf Baechle [this message]
     [not found]   ` <20020716090728.A22128@lucon.org>
2002-07-16 19:16     ` PATCH: Add sys/personality (Re: Personality) Carsten Langgaard
     [not found]       ` <20020716190814.A31309@lucon.org>
2002-07-17  7:14         ` Carsten Langgaard
2002-07-16 13:40 ` Personality Daniel Jacobowitz
2002-07-16 13:57   ` Personality Carsten Langgaard

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=20020716123632.B17038@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=carstenl@mips.com \
    --cc=hjl@lucon.org \
    --cc=linux-mips@oss.sgi.com \
    /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