linux-kernel - Re: next-20080808: bash: fork: Resource temporarily unavailable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <13299.1218367912@redhat.com>
Date:	Sun, 10 Aug 2008 12:31:52 +0100
From:	David Howells <dhowells@...hat.com>
To:	Grant Wilson <grant.wilson@....co.uk>
Cc:	dhowells@...hat.com, Jasper Bryant-Greene <jasper@...ton.co.nz>,
	Thomas Meyer <thomas@...3r.de>,
	James Morris <jmorris@...ei.org>,
	Linux-Kernel <linux-kernel@...r.kernel.org>,
	Linux-Next <linux-next@...r.kernel.org>
Subject: Re: next-20080808: bash: fork: Resource temporarily unavailable

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

> On Sun, 10 Aug 2008 10:45:39 +0100
> David Howells <dhowells@...hat.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/