From: Arnd Bergmann <arnd@arndb.de>
To: liqin.chen@sunplusct.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH 07/27] score: create head files elf.h emergency-restart.h errno.h
Date: Sun, 14 Jun 2009 00:23:06 +0200 [thread overview]
Message-ID: <200906140023.06690.arnd@arndb.de> (raw)
In-Reply-To: <OF33B57F6A.69479DBB-ON482575D4.00247552-482575D4.002503BB@sunplusct.com>
On Saturday 13 June 2009, liqin.chen@sunplusct.com wrote:
> >
> > EMAXERRNO is mips specific right now. Do you actually need it somewhere?
> >
>
> Yes, I used it in entry.S, maybe I could remove this define latter.
>
Ok. Note that the maximum error number that is supposed to get sent back
to user space is 511. Most architectures check the return value of the
system call to be between -4095 and zero upon entering user space.
Checking it in the kernel gives you the chance to override the
error status from a system call with force_successful_syscall_return().
If that is your intention, you should probably leave the definition in there.
Powerpc uses _LAST_ERRNO for the same purpose, which is somewhat inconsistent
with mips and also uses a different value to compare against.
Arnd <><
next prev parent reply other threads:[~2009-06-13 22:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 6:26 [PATCH 07/27] score: create head files elf.h emergency-restart.h errno.h liqin.chen
2009-06-09 17:20 ` Arnd Bergmann
2009-06-13 6:39 ` liqin.chen
2009-06-13 22:23 ` Arnd Bergmann [this message]
2009-06-15 12:11 ` liqin.chen
2009-06-15 13:30 ` [PATCH] asm-generic: add EMAXERRNO Arnd Bergmann
2009-06-15 13:31 ` Matthew Wilcox
2009-06-15 14:02 ` Arnd Bergmann
2009-06-16 3:04 ` liqin.chen
2009-06-16 14:13 ` Arnd Bergmann
2009-06-15 13:33 ` liqin.chen
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=200906140023.06690.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqin.chen@sunplusct.com \
--cc=torvalds@linux-foundation.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