mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Will Deacon <will@kernel.org>
Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
	netdev@vger.kernel.org, viro@zeniv.linux.org.uk,
	brauner@kernel.org, davem@davemloft.net, edumazet@google.com,
	hdanton@sina.com, kuba@kernel.org, jasowang@redhat.com,
	mst@redhat.com, pabeni@redhat.com, stefanha@redhat.com,
	sgarzare@redhat.com
Subject: Re: [PATCH 0/2] Fix vsock error-handling regression introduced in v6.17-rc1
Date: Fri, 22 Aug 2025 01:20:11 +0000	[thread overview]
Message-ID: <175582561148.1263133.8095775634903727151.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250818180355.29275-1-will@kernel.org>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 18 Aug 2025 19:03:53 +0100 you 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,
> 
> [...]

Here is the summary with links:
  - [1/2] net: Introduce skb_copy_datagram_from_iter_full()
    https://git.kernel.org/netdev/net/c/b08a784a5d14
  - [2/2] vsock/virtio: Fix message iterator handling on transmit path
    https://git.kernel.org/netdev/net/c/7fb1291257ea

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



      parent reply	other threads:[~2025-08-22  1:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 18:03 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
2025-08-22  1:20 ` 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=175582561148.1263133.8095775634903727151.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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=stefanha@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
all inboxes | Powered by JetHome®