All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: edumazet@google.com, netdev@vger.kernel.org, sara@sinodun.com,
	ycheng@google.com
Subject: Re: [PATCH net-next 0/2] tcp: fastopen: accept data/FIN present in SYNACK
Date: Sat, 06 Feb 2016 10:52:11 -0800	[thread overview]
Message-ID: <1454784731.7627.329.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <20160206.031302.1262914455786911151.davem@davemloft.net>

On Sat, 2016-02-06 at 03:13 -0500, David Miller wrote:
> From: Eric Dumazet <edumazet@google.com>
> Date: Mon,  1 Feb 2016 21:03:06 -0800
> 
> > Implements RFC 7413 (TCP Fast Open) 4.2.2, accepting payload and/or FIN
> > in SYNACK messages, and prepare removal of SYN flag in tcp_recvmsg()
> 
> Series applied, thanks Eric.

It seems I missed to call tcp_fin() if a FIN flag was present.

(But then we had this issue before my patches, Yuchung, for a SYN packet
+ FIN  ?)

I will send a followup.

Thanks David.

  reply	other threads:[~2016-02-06 18:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  5:03 [PATCH net-next 0/2] tcp: fastopen: accept data/FIN present in SYNACK Eric Dumazet
2016-02-02  5:03 ` [PATCH net-next 1/2] tcp: fastopen: accept data/FIN present in SYNACK message Eric Dumazet
2016-02-02  5:03 ` [PATCH net-next 2/2] tcp: do not enqueue skb with SYN flag Eric Dumazet
2016-02-06  8:13 ` [PATCH net-next 0/2] tcp: fastopen: accept data/FIN present in SYNACK David Miller
2016-02-06 18:52   ` Eric Dumazet [this message]
2016-02-06 19:16     ` [PATCH net-next] tcp: fastopen: call tcp_fin() if FIN " Eric Dumazet
2016-02-06 21:50       ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1454784731.7627.329.camel@edumazet-glaptop2.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=sara@sinodun.com \
    --cc=ycheng@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.