From: patchwork-bot+netdevbpf@kernel.org
To: Arseniy Krasnov <avkrasnov@salutedevices.com>
Cc: stefanha@redhat.com, sgarzare@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
mst@redhat.com, jasowang@redhat.com,
bobby.eshleman@bytedance.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@sberdevices.ru, oxffffaa@gmail.com
Subject: Re: [PATCH net-next v2 0/2] vsock: handle writes to shutdowned socket
Date: Thu, 14 Sep 2023 06:40:26 +0000 [thread overview]
Message-ID: <169467362675.3965.13004245491744168784.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230911202027.1928574-1-avkrasnov@salutedevices.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 11 Sep 2023 23:20:25 +0300 you wrote:
> Hello,
>
> this small patchset adds POSIX compliant behaviour on writes to the
> socket which was shutdowned with 'shutdown()' (both sides - local with
> SHUT_WR flag, peer - with SHUT_RD flag). According POSIX we must send
> SIGPIPE in such cases (but SIGPIPE is not send when MSG_NOSIGNAL is set).
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] vsock: send SIGPIPE on write to shutdowned socket
https://git.kernel.org/netdev/net-next/c/8ecf0cedc08a
- [net-next,v2,2/2] test/vsock: shutdowned socket test
https://git.kernel.org/netdev/net-next/c/b698bd97c571
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-09-14 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 20:20 [PATCH net-next v2 0/2] vsock: handle writes to shutdowned socket Arseniy Krasnov
2023-09-11 20:20 ` [PATCH net-next v2 1/2] vsock: send SIGPIPE on write " Arseniy Krasnov
2023-09-11 20:20 ` [PATCH net-next v2 2/2] test/vsock: shutdowned socket test Arseniy Krasnov
2023-09-14 6:40 ` 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=169467362675.3965.13004245491744168784.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=avkrasnov@salutedevices.com \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kernel@sberdevices.ru \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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