The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, virtualization@lists.linux.dev,
	kuba@kernel.org, linux-kernel@vger.kernel.org,
	leonardi@redhat.com
Subject: Re: [PATCH net-next] vsock/test: fix test for null ptr deref when transport changes
Date: Thu, 10 Jul 2025 03:00:28 +0000	[thread overview]
Message-ID: <175211642825.969691.15727844419964289216.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250708111701.129585-1-sgarzare@redhat.com>

Hello:

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

On Tue,  8 Jul 2025 13:17:01 +0200 you wrote:
> From: Stefano Garzarella <sgarzare@redhat.com>
> 
> In test_stream_transport_change_client(), the client sends CONTROL_CONTINUE
> on each iteration, even when connect() is unsuccessful. This causes a flood
> of control messages in the server that hangs around for more than 10
> seconds after the test finishes, triggering several timeouts and causing
> subsequent tests to fail. This was discovered in testing a newly proposed
> test that failed in this way on the client side:
>     ...
>     33 - SOCK_STREAM transport change null-ptr-deref...ok
>     34 - SOCK_STREAM ioctl(SIOCINQ) functionality...recv timed out
> 
> [...]

Here is the summary with links:
  - [net-next] vsock/test: fix test for null ptr deref when transport changes
    https://git.kernel.org/netdev/net-next/c/5d6fc6b4d0b2

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-07-10  3:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 11:17 [PATCH net-next] vsock/test: fix test for null ptr deref when transport changes Stefano Garzarella
2025-07-08 12:15 ` Luigi Leonardi
2025-07-10  3:00 ` 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=175211642825.969691.15727844419964289216.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leonardi@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --cc=virtualization@lists.linux.dev \
    /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