public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@karaya.com>
To: Lennert Buytenhek <buytenh@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] global errno considered harmful
Date: Sun, 30 Dec 2001 14:56:21 -0500	[thread overview]
Message-ID: <200112301956.OAA02630@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Sun, 30 Dec 2001 11:06:23 EST." <20011230110623.A17083@gnu.org>

buytenh@gnu.org said:
> Is there any particular reason we need a global errno in the kernel at
> all? (which, by the way, doesn't seem to be subject to any kind of
> locking)  

As far as I've been able to tell, no.

> It makes life for User Mode Linux somewhat more complicated
> than it could be, and it generally just seems a bad idea.

Yeah.  In order for -fno-common to not blow up the UML build (because of the
clash between libc errno and kernel errno), I had to add -Derrno=kernel_errno
to all the kernel file compiles.  It would be nice to get rid of that wart.

> Referenced patch deletes all mention of a global errno from the
> kernel

Awesome.  This definitely needs to happen.  If no one spots any breakage,
send it in...

> and fixes up callers where necessary.

I did some grepping and the only problem I noticed was UML's execve (heh)
converting a -errno return to a -1.

				Jeff


  reply	other threads:[~2001-12-30 18:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-30 16:06 [PATCH][RFC] global errno considered harmful Lennert Buytenhek
2001-12-30 19:56 ` Jeff Dike [this message]
2001-12-30 21:00   ` Ralf Baechle
2001-12-30 22:10     ` Brian Gerst
2001-12-31  1:59       ` Ralf Baechle
2001-12-31 16:48         ` Andreas Schwab
2001-12-31 21:42           ` Ralf Baechle
2001-12-31  1:52     ` Lennert Buytenhek
2001-12-31  2:01       ` Ralf Baechle
2001-12-31 20:56         ` Erik Andersen
2001-12-31  0:01 ` ertzog

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=200112301956.OAA02630@ccure.karaya.com \
    --to=jdike@karaya.com \
    --cc=buytenh@gnu.org \
    --cc=linux-kernel@vger.kernel.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