To: "Phil Endecott" <phil_wueww_endecott@chezphil.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: strace, accept(), ERESTARTSYS and EINTR
From: Andi Kleen <andi@firstfloor.org>
References: <1199480498017@dmwebmail.japan.chezphil.org>
Date: Sat, 05 Jan 2008 16:03:11 +0100
In-Reply-To: <1199480498017@dmwebmail.japan.chezphil.org> (Phil Endecott's message of "Fri\, 04 Jan 2008 21\:01\:38 +0000")
Message-ID: <p731w8w8gcw.fsf@bingen.suse.de>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1471
Lines: 42

"Phil Endecott" <phil_wueww_endecott@chezphil.org> writes:
>
> Many thanks for any suggestions.

It's a long standing bug reported regularly but so far nobody has tracked 
it down. That's mostly because most people cannot really reproduce it.

If you can reproduce it reliably: you could do the brute force debugging 
method. Simply grep all  places in the kernel code that set or pass ERESTART
and add a 

    printk("%s:%d ERESTART\n", __FILE__, __LINE__);

or perhaps

   printk("%s:%d %s:%d ERESTART\n", current->comm, current->pid, __FILE__,
               __LINE__);

or perhaps

   if (!strcmp(current->comm, "yourprogramwithoutpath"))
            printk("%s:%d ERESTART\n", __FILE__, __LINE__);

[the later two might need adding linux/string.h and/or linux/sched.h includes
to the files if they don't compile]

to all of them. Then recompile and boot that kernel.

Now if you can match such a output line to your program 
malfunction we would know where the problem is and then it would be likely
reasonable easy to fix.

Note that the above first two might produce a lot of output if you're
unlucky -- definitely don't do it on a production machine and kill
syslog first so that it doesn't all end up on disk.

-Andi
--
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/