From: patchwork-bot+netdevbpf@kernel.org
To: Ziyu Zhang <ziyuzhang201@gmail.com>
Cc: sgarzare@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
acking@vmware.com, georgezhang@vmware.com, dtor@vmware.com,
kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, longli@microsoft.com, stefanha@redhat.com,
mst@redhat.com, jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com, bryan-bt.tan@broadcom.com,
vishnu.dasa@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org,
kvm@vger.kernel.org, baijiaju1990@gmail.com, r33s3n6@gmail.com,
gality369@gmail.com, zhenghaoran154@gmail.com,
hanguidong02@gmail.com, zzzccc427@gmail.com
Subject: Re: [PATCH net v2] vsock: keep poll shutdown state consistent
Date: Fri, 22 May 2026 18:30:05 +0000 [thread overview]
Message-ID: <177947460540.1324219.4145730624585924301.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260519165636.62542-1-ziyuzhang201@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 20 May 2026 00:56:36 +0800 you wrote:
> vsock_poll() reads vsk->peer_shutdown before taking the socket lock
> to set EPOLLHUP and EPOLLRDHUP, then reads it again after taking
> the lock to report EOF readability. A shutdown packet can update
> peer_shutdown while poll is waiting for the lock, so one poll invocation
> can report EOF readability without the corresponding HUP/RDHUP bits.
>
> For connectible sockets, take one peer_shutdown snapshot after
> lock_sock() and use it for all peer-shutdown-derived poll bits. For
> datagram sockets, which do not take lock_sock() in poll(), take one
> lockless READ_ONCE() snapshot and pair it with WRITE_ONCE() on the
> writer side.
>
> [...]
Here is the summary with links:
- [net,v2] vsock: keep poll shutdown state consistent
https://git.kernel.org/netdev/net/c/aae9d8a5528b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-05-22 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 16:56 [PATCH net v2] vsock: keep poll shutdown state consistent Ziyu Zhang
2026-05-22 18:30 ` patchwork-bot+netdevbpf [this message]
2026-05-30 0:44 ` sashiko-bot
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=177947460540.1324219.4145730624585924301.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acking@vmware.com \
--cc=baijiaju1990@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bryan-bt.tan@broadcom.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=dtor@vmware.com \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=gality369@gmail.com \
--cc=georgezhang@vmware.com \
--cc=haiyangz@microsoft.com \
--cc=hanguidong02@gmail.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=r33s3n6@gmail.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=vishnu.dasa@broadcom.com \
--cc=wei.liu@kernel.org \
--cc=xuanzhuo@linux.alibaba.com \
--cc=zhenghaoran154@gmail.com \
--cc=ziyuzhang201@gmail.com \
--cc=zzzccc427@gmail.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