netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	edumazet@google.com, weiwan@google.com, arjunroy@google.com
Subject: Re: [PATCH net-next] tcp: tcp_data_ready() must look at SOCK_DONE
Date: Mon, 15 Feb 2021 21:30:07 +0000	[thread overview]
Message-ID: <161342460797.27343.6265387962424885407.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210213142634.3237642-1-eric.dumazet@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Sat, 13 Feb 2021 06:26:34 -0800 you wrote:
> From: Eric Dumazet <edumazet@google.com>
> 
> My prior cleanup missed that tcp_data_ready() has to look at SOCK_DONE.
> Otherwise, an application using SO_RCVLOWAT will not get EPOLLIN event
> if a FIN is received in the middle of expected payload.
> 
> The reason SOCK_DONE is not examined in tcp_epollin_ready()
> is that tcp_poll() catches the FIN because tcp_fin()
> is also setting RCV_SHUTDOWN into sk->sk_shutdown
> 
> [...]

Here is the summary with links:
  - [net-next] tcp: tcp_data_ready() must look at SOCK_DONE
    https://git.kernel.org/netdev/net-next/c/39354eb29f59

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-02-15 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-13 14:26 [PATCH net-next] tcp: tcp_data_ready() must look at SOCK_DONE Eric Dumazet
2021-02-14 18:34 ` Wei Wang
2021-02-15 21:30 ` patchwork-bot+netdevbpf [this message]

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=161342460797.27343.6265387962424885407.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=arjunroy@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=weiwan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).