To: "Andi Kleen" <andi@firstfloor.org>
Cc: <linux-kernel@vger.kernel.org>
Date: Sat, 05 Jan 2008 18:42:24 +0000
Subject: Re: strace, accept(), ERESTARTSYS and EINTR
Message-ID: <1199558544071@dmwebmail.japan.chezphil.org>
In-Reply-To: <p731w8w8gcw.fsf@bingen.suse.de>
References: <p731w8w8gcw.fsf@bingen.suse.de>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
From: "Phil Endecott" <phil_wueww_endecott@chezphil.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1208
Lines: 37

Andi Kleen wrote:
> "Phil Endecott" <phil_wueww_endecott@chezphil.org> writes:
>>
>> Many thanks for any suggestions.
>
> It's a long standing bug reported regularly

Thanks for the re-assurance.

> but so far nobody has tracked 
> it down. That's mostly because most people cannot really reproduce it.

I'm pretty sure that it's triggered by some earlier problem, most 
likely reaching a threads-per-process limit (or an associated total VM 
per process limit due to large default thread stack sizes).  There's a 
good chance that I will find and fix that problem, and this one will 
then go away unsolved...

> If you can reproduce it reliably
[snip]
> definitely don't do it on a production machine

Unfortunately, it happens on the production machine but I've not been 
able to reproduce it otherwise.  I'll keep trying.  FWIW my assumption 
is that the ERESTARTSYS comes from the sock_intr_errno() call from inet_csk_wait_for_connect().


Thanks,  Phil.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/