public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: "Nikita V. Youshchenko" <yoush@cs.msu.su>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Extended error reporting to user space?
Date: Sun, 21 Feb 2010 00:02:29 +0000	[thread overview]
Message-ID: <20100221000229.GA8092@gallifrey> (raw)
In-Reply-To: <20100217202312.GQ21783@one.firstfloor.org>

* Andi Kleen (andi@firstfloor.org) wrote:
> > I'd wondered about some form of halfway house where the error
> > value is expanded but could be truncated for compatibility - i.e.
> 
> Who would do the truncation?

I'd assumed something like the code in entry*.S or equivalent for
existing syscalls, but have another entry that would pass it through
to a newer libc that new how to handle it.

> > if at the moment we had:
> > 
> >     return -EINVAL;
> > 
> > it would become:
> > 
> >     return ERRORNUM(EINVAL, BADLENGTH);
> 
> x86 only has about 12 bits in the current ABI btw.

Ah yes I can see that now, hmm.

Dave
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2010-02-21  0:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16 12:20 Extended error reporting to user space? Nikita V. Youshchenko
2010-02-16 12:23 ` Alexey Dobriyan
2010-02-16 13:17   ` Américo Wang
2010-02-17  9:58 ` Andi Kleen
2010-02-17 10:16   ` Nikita V. Youshchenko
2010-02-17 10:35     ` Andi Kleen
2010-02-17 19:20       ` Dr. David Alan Gilbert
2010-02-17 20:23         ` Andi Kleen
2010-02-21  0:02           ` Dr. David Alan Gilbert [this message]
2010-02-17 10:43     ` Alan Cox
2010-02-17 11:57       ` Andi Kleen

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=20100221000229.GA8092@gallifrey \
    --to=linux@treblig.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yoush@cs.msu.su \
    /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