Re: TCP connections come in wrong order

From: One Thousand Gnomes
Date: Mon Feb 02 2015 - 10:08:00 EST

Next message: Peter Zijlstra: "Re: [PATCH 0/1] futex: check PF_KTHREAD rather than !p->mm to filter out kthreads"
Previous message: Tadeusz Struk: "Re: [PATCH 0/3] crypto: algif - change algif_skcipher to be asynchronous"
In reply to: Askar Safin: "TCP connections come in wrong order"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> If 'diff' doesn't report difference, then try again and again.
>
> Is this a bug? I think that this is a bug.
>
> Linux ideal-os 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux
> Debian 8.0 Jessie
> GNU C Library (Debian GLIBC 2.19-13) stable release version 2.19, by Roland McGrath et al.
> ==

No it's not a bug. Nothing in SuS or traditional BSD sockets guarantees
that connections are processed in strict time sequenced incoming order.

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

Next message: Peter Zijlstra: "Re: [PATCH 0/1] futex: check PF_KTHREAD rather than !p->mm to filter out kthreads"
Previous message: Tadeusz Struk: "Re: [PATCH 0/3] crypto: algif - change algif_skcipher to be asynchronous"
In reply to: Askar Safin: "TCP connections come in wrong order"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]