public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Grant Wilson <grant.wilson@zen.co.uk>
Cc: dhowells@redhat.com, Jasper Bryant-Greene <jasper@amiton.co.nz>,
	Thomas Meyer <thomas@m3y3r.de>, James Morris <jmorris@namei.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	Linux-Next <linux-next@vger.kernel.org>
Subject: Re: next-20080808: bash: fork: Resource temporarily unavailable
Date: Sun, 10 Aug 2008 12:31:52 +0100	[thread overview]
Message-ID: <13299.1218367912@redhat.com> (raw)
In-Reply-To: <20080810113044.19143b0a@worthy.swandive.local>

Grant Wilson <grant.wilson@zen.co.uk> wrote:

> On Sun, 10 Aug 2008 10:45:39 +0100
> David Howells <dhowells@redhat.com> wrote:
> 
> [snip]
> > 
> > Are you running as an unprivileged user?  If so, this may be the point
> > that's biting you.  Can you try applying the attached patch to find more
> > information?
> [snip]
> I'm also experiencing this on an X86_64 system as an unprivileged user.

Thanks for your help.

> With your patch applied I get the following repeated several times
> during the boot, but with no apparent ill effects:
> 
> [   31.033195] copy_process() = -513 

That's probably nothing to worry about.  It -ERESTARTNOINTR, indicating, I
would guess, that fork() was interrupted by a signal.

> When the fork call starts to fail after a few minutes the following is logged:
> 
> [  223.039938] Rlimit EAGAIN (-1 >= 16375, uid 1000)
> [  223.044744] copy_process() = -11
> [  226.660319] Rlimit EAGAIN (-1 >= 16375, uid 1000)
> [  226.664166] copy_process() = -11

Okay.  That's useful, thanks.  That indicates that my accounting of user
processes is incorrect somewhere.  This won't show up when running as a
privileged user only.

David

  reply	other threads:[~2008-08-10 11:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 17:02 next-20080808: bash: fork: Resource temporarily unavailable Thomas Meyer
2008-08-08 17:21 ` Adrian Bunk
2008-08-08 22:32   ` David Howells
2008-08-08 22:48     ` James Morris
2008-08-08 23:23       ` David Howells
2008-08-08 21:48 ` James Morris
2008-08-09  8:44   ` jasper
2008-08-09  8:46     ` jasper
2008-08-09 11:26   ` Thomas Meyer
2008-08-09 12:52     ` David Howells
2008-08-09 13:11       ` Thomas Meyer
2008-08-09 14:07         ` David Howells
2008-08-09 22:55           ` Jasper Bryant-Greene
2008-08-10  9:45             ` David Howells
2008-08-10 10:30               ` Grant Wilson
2008-08-10 11:31                 ` David Howells [this message]
2008-08-11  0:26                   ` James Morris
2008-08-11  0:21                 ` David Howells
2008-08-11  0:44                   ` James Morris

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=13299.1218367912@redhat.com \
    --to=dhowells@redhat.com \
    --cc=grant.wilson@zen.co.uk \
    --cc=jasper@amiton.co.nz \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=thomas@m3y3r.de \
    /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