netdev - Re: [PATCH] tcp: make urg+gso work for real this time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20081225.180051.116331110.davem@davemloft.net>
Date:	Thu, 25 Dec 2008 18:00:51 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	herbert@...dor.apana.org.au
Cc:	ilpo.jarvinen@...sinki.fi, kuznet@....inr.ac.ru, ptesarik@...e.cz,
	netdev@...r.kernel.org
Subject: Re: [PATCH] tcp: make urg+gso work for real this time

From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Fri, 26 Dec 2008 12:47:39 +1100

> If all these packets are delivered in order, then what'll happen
> is that RCV.UP starts out at 65535, and once the final segment is
> delivered it'll be updated to 66240.
> 
> If out-of-order delivery occurs and the final segment arrives earlier,
> then all that'll happen is that RCV.UP will hit 66240 earlier, which
> is not an issue since all subsequent urgent pointers will be less and
> hence ignored.

So it all hinges on how the receiver updates his URG pointer.  This is
what legitimizes a sender advertising a changing URG pointer.

So it works, but it isn't the nicest thing in the world :-)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html