Re: Help: error 514 in select()

From: Baurzhan Ismagulov
Date: Wed Aug 23 2006 - 19:20:08 EST

Hello Misha,

On Mon, Aug 21, 2006 at 06:49:03PM -0700, Misha Sushchik wrote:
> 1) I do not know when this problem first appeared (or, re-appeared, as
> I can see from searching the web). If we knew the latest version where
> this problem was not, we would consider just going back to that
> version, instead of waiting for the bug to be fixed.

It would be fairly easy to find out once you have (2) solved.

> 2) I do not have a sensible way of reproducing this error in a short
> time. It may take a few days of running our application in order for
> it to fail in this way. This is killing us (timewise) in testing
> possible solutions.

I would start with the following:

1. Do you know all signals sent to the process in question by itself or
by other processes? Can you log them?

2. Have you tried the patch from my last mail?

This may help to understand how the problem can be reproduced. My
current assumption is, your process calls select(2), a signal arrives,
ERESTARTNOHAND is not replaced with EINTR and the former is leaked to
the user space; you have to find out where the return value should be
replaced, and make it happen. If there are many ERESTARTNOHANDs during
the normal operation, printing the stack just before returning to user
space could help further.

> The latest kernel we had this reproduced with was 2.6.17.

Good to know! I assume you haven't tried, right? Although,
after a quick skimming through the changes since 2.6.17, I haven't seen
anything that could be relevant.

With kind regards,
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at