> > thinking there is no data available. Secondary problem is that the kernel > > returns the wrong thing when the syscall is interrupted. > > But I just tried this on my x86 as well (2.2 kernel): The return is ok. Its 'deep magic' strace sees