Re: recvmsg bug: copied 0 seq XXXXX

Andi Kleen (ak@muc.de)
05 Oct 1999 13:55:12 +0200


alan@lxorguk.ukuu.org.uk (Alan Cox) writes:

> > I'm still getting this messages in kernel 2.2.13pre15.
> > The oldest message that appears in my logs is with a 2.2.12 kernel.
> > I don't know if they have appeared before.
>
> It implies a possible problem but its non fatal. It may in fact just
> be a race updating those variables

copied_seq should be protected by the kernel log in 2.2, and interrupts do
never touch it.

-Andi

-- 
This is like TV. I don't like TV.

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