linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>,
	"Christopher S. Aker" <caker@theshore.net>
Subject: Re: [uml-devel] init_new_context_skas - new_mm failed, errno = -24
Date: Tue, 11 Sep 2007 17:14:06 +0200	[thread overview]
Message-ID: <200709111714.14572.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20070911145852.GB7551@c2.user-mode-linux.org>


[-- Attachment #1.1: Type: text/plain, Size: 1077 bytes --]

On martedì 11 settembre 2007, Jeff Dike wrote:
> On Tue, Sep 11, 2007 at 04:00:58PM +0200, Blaisorblade wrote:
> > errno = 24 means EMFILE (too many open files).
>
> Whoops, I mentally turned that into -ENOMEM.
>
> Maybe we should resurrect os_print_error as you suggested and start
> using it.  The current habit of using raw errnos dates from very
> early, when perror (or strerror - I don't remember which) gave me
> undebuggable segfaults deep inside libc.  Probably, that's not a
> problem any more.

I surely agree. I also think I had introduced os_print_error and exactly for 
this purpose, even if I can't recall well.

strerror() is not reentrant so it can't be used, but there is strerror_r.

There is no strsignal_r (using strsignal(3) would clear messages as "Kernel 
mode signal 8"), but I'd suggest to follow the unrecommended but documented 
practice of using sys_siglist[signr].
-- 
"Doh!" (cit.), I've made another mistake!
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 194 bytes --]

_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2007-09-11 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06 15:03 [uml-devel] init_new_context_skas - new_mm failed, errno = -24 Christopher S. Aker
2007-09-10 16:14 ` Jeff Dike
2007-09-10 23:06   ` Christopher S. Aker
2007-09-11 14:00     ` Blaisorblade
2007-09-11 14:58       ` Jeff Dike
2007-09-11 15:14         ` Blaisorblade [this message]
2007-09-21 18:41       ` Jeff Dike

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=200709111714.14572.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=caker@theshore.net \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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