mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrea Parri <parri.andrea@gmail.com>
Cc: sgarzare@redhat.com, haiyangz@microsoft.com, wei.liu@kernel.org,
	decui@microsoft.com, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, bobbyeshleman@meta.com,
	horms@kernel.org, leonardi@redhat.com,
	niuxuewei.nxw@antgroup.com, linux-hyperv@vger.kernel.org,
	virtualization@lists.linux.dev, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] hv_sock: Report no unread data before a channel is available
Date: Tue, 10 Nov 2026 22:30:06 +0000	[thread overview]
Message-ID: <179434980692.92301.5684137736887990228.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106123920.162131-1-parri.andrea@gmail.com>

Hello:

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

On Fri,  6 Nov 2026 13:39:18 +0100 you wrote:
> The Hyper-V transport is assigned before the asynchronous VMBus channel
> offer completes.  Its zero-initialized hvsock therefore has a NULL chan
> until hvs_open_connection() associates the channel with the socket.
> 
> SIOCINQ can query the assigned transport while the socket is connecting,
> or after connect() fails once the transport has been assigned.  Unlike
> poll(), that path does not check stream_is_active() before calling the
> transport's stream_has_data callback.  hvs_stream_has_data() then passes
> the NULL channel to hvs_channel_readable_payload(), and any user in the
> guest can trigger an oops:
> 
> [...]

Here is the summary with links:
  - [net] hv_sock: Report no unread data before a channel is available
    https://git.kernel.org/netdev/net/c/71b06766b7c4

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



      parent reply	other threads:[~2026-11-10 22:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 12:39 Andrea Parri
2026-11-06 14:39 ` Stefano Garzarella
2026-11-06 15:04 ` Luigi Leonardi
2026-11-10 22: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=179434980692.92301.5684137736887990228.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bobbyeshleman@meta.com \
    --cc=davem@davemloft.net \
    --cc=decui@microsoft.com \
    --cc=edumazet@kernel.org \
    --cc=haiyangz@microsoft.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leonardi@redhat.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=niuxuewei.nxw@antgroup.com \
    --cc=pabeni@redhat.com \
    --cc=parri.andrea@gmail.com \
    --cc=sgarzare@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=wei.liu@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®