From: Stefan Hajnoczi <stefanha@redhat.com>
To: Will Deacon <will@kernel.org>
Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
netdev@vger.kernel.org, Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Hillf Danton <hdanton@sina.com>, Jakub Kicinski <kuba@kernel.org>,
Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Abeni <pabeni@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [PATCH 0/2] Fix vsock error-handling regression introduced in v6.17-rc1
Date: Tue, 19 Aug 2025 07:42:23 -0400 [thread overview]
Message-ID: <20250819114223.GA37216@fedora> (raw)
In-Reply-To: <20250818180355.29275-1-will@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
On Mon, Aug 18, 2025 at 07:03:53PM +0100, Will Deacon wrote:
> Hi all,
>
> Here are a couple of patches fixing the vsock error-handling regression
> found by syzbot [1] that I introduced during the recent merge window.
>
> Cheers,
>
> Will
>
> [1] https://lore.kernel.org/all/689a3d92.050a0220.7f033.00ff.GAE@google.com/
>
> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> Cc: Christian Brauner <brauner@kernel.org>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: Hillf Danton <hdanton@sina.com>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Jason Wang <jasowang@redhat.com>
> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> Cc: Paolo Abeni <pabeni@redhat.com>
> Cc: Stefan Hajnoczi <stefanha@redhat.com>
> Cc: Stefano Garzarella <sgarzare@redhat.com>
>
> --->8
>
> Will Deacon (2):
> net: Introduce skb_copy_datagram_from_iter_full()
> vsock/virtio: Fix message iterator handling on transmit path
>
> include/linux/skbuff.h | 2 ++
> net/core/datagram.c | 14 ++++++++++++++
> net/vmw_vsock/virtio_transport_common.c | 8 +++++---
> 3 files changed, 21 insertions(+), 3 deletions(-)
>
> --
> 2.51.0.rc1.167.g924127e9c0-goog
>
Stefano Garzarella is offline at the moment and may not get a chance to
review this for another week. In the meantime I have reviewed this patch
series:
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-08-19 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 18:03 [PATCH 0/2] Fix vsock error-handling regression introduced in v6.17-rc1 Will Deacon
2025-08-18 18:03 ` [PATCH 1/2] net: Introduce skb_copy_datagram_from_iter_full() Will Deacon
2025-08-18 18:03 ` [PATCH 2/2] vsock/virtio: Fix message iterator handling on transmit path Will Deacon
2025-08-19 11:12 ` [PATCH 0/2] Fix vsock error-handling regression introduced in v6.17-rc1 Michael S. Tsirkin
2025-08-19 11:42 ` Stefan Hajnoczi [this message]
2025-08-22 1:20 ` patchwork-bot+netdevbpf
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=20250819114223.GA37216@fedora \
--to=stefanha@redhat.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=virtualization@lists.linux.dev \
--cc=will@kernel.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