From: patchwork-bot+netdevbpf@kernel.org
To: Luigi Leonardi <leonardi@redhat.com>
Cc: sgarzare@redhat.com, mhal@rbox.co,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, v4bel@theori.io
Subject: Re: [PATCH net-next v5 0/2] vsock/test: check for null-ptr-deref when transport changes
Date: Wed, 02 Jul 2025 22:10:18 +0000 [thread overview]
Message-ID: <175149421852.880958.2267233099494206987.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250630-test_vsock-v5-0-2492e141e80b@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Jun 2025 18:33:02 +0200 you wrote:
> This series introduces a new test that checks for a null pointer
> dereference that may happen when there is a transport change[1]. This
> bug was fixed in [2].
>
> Note that this test *cannot* fail, it hangs if it triggers a kernel
> oops. The intended use-case is to run it and then check if there is any
> oops in the dmesg.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] vsock/test: Add macros to identify transports
https://git.kernel.org/netdev/net-next/c/e84b20b25d37
- [net-next,v5,2/2] vsock/test: Add test for null ptr deref when transport changes
https://git.kernel.org/netdev/net-next/c/3a764d93385c
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:[~2025-07-02 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 16:33 [PATCH net-next v5 0/2] vsock/test: check for null-ptr-deref when transport changes Luigi Leonardi
2025-06-30 16:33 ` [PATCH net-next v5 1/2] vsock/test: Add macros to identify transports Luigi Leonardi
2025-07-02 11:17 ` Stefano Garzarella
2025-06-30 16:33 ` [PATCH net-next v5 2/2] vsock/test: Add test for null ptr deref when transport changes Luigi Leonardi
2025-07-02 11:17 ` Stefano Garzarella
2025-07-02 22:10 ` 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=175149421852.880958.2267233099494206987.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=leonardi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=v4bel@theori.io \
--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