netdev - Re: [PATCH net-next] remove an outdated reference to T/TCP

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAK6E8=cne1UbOEcZ6ZfsJw-=qwUsO=yMEi3LNNsTpM_5crv0fg@mail.gmail.com>
Date:	Tue, 6 Dec 2011 15:00:13 -0800
From:	Yuchung Cheng <ycheng@...gle.com>
To:	David Miller <davem@...emloft.net>
Cc:	rick.jones2@...com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] remove an outdated reference to T/TCP

On Tue, Dec 6, 2011 at 1:42 PM, David Miller <davem@...emloft.net> wrote:
>
> From: Rick Jones <rick.jones2@...com>
> Date: Tue, 06 Dec 2011 13:39:23 -0800
>
> > On 12/06/2011 12:19 PM, David Miller wrote:
> >> From: Rick Jones<rick.jones2@...com>
> >> Date: Tue,  6 Dec 2011 12:00:05 -0800 (PST)
> >>
> >>>
> >>> Remove a particularly out of date bit of comment referring to T/TCP.
> >>>
> >>> Signed-off-by: Rick Jones<rick.jones2@...com>
> >>
> >> I think it should stay because it discusses the potential bad side
> >> effects of queueing any data that might be in the SYN.
> >
> > How about just the sentence that mentioned T/TCP explicitly since
> > T/TCP is most definitely no longer starting to be used?-) The rest of
> > it can be discussed when/if TCP Fast Open arrives :)
>
> T/TCP gives the statement context, as in referencing something that
> might make us want to at least theoretically consider handling the
> data.
I am fine keeping the comment as is.  This does remind me to put more
comments on this part of the code in our upcoming Fast Open patch :)
--
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