From: Jakub Kicinski <kuba@kernel.org>
To: Michal Luczaj <mhal@rbox.co>
Cc: Stefano Garzarella <sgarzare@redhat.com>,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/3] vsock/test: Improve transport_uaf test
Date: Mon, 16 Jun 2025 14:57:29 -0700 [thread overview]
Message-ID: <20250616145729.1a16afdc@kernel.org> (raw)
In-Reply-To: <20250611-vsock-test-inc-cov-v3-0-5834060d9c20@rbox.co>
On Wed, 11 Jun 2025 21:56:49 +0200 Michal Luczaj wrote:
> Increase the coverage of a test implemented in commit 301a62dfb0d0
> ("vsock/test: Add test for UAF due to socket unbinding"). Take this
> opportunity to factor out some utility code, drop a redundant sync between
> client and server, and introduce a /proc/kallsyms harvesting logic for
> auto-detecting registered vsock transports.
Hi Stefano! Sorry to ping, are these on your radar?
I'm wondering if the delay is because of devconf.cz or you consider
the Suggested-by tags a strong enough indication of support :)
next prev parent reply other threads:[~2025-06-16 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 19:56 [PATCH net-next v3 0/3] vsock/test: Improve transport_uaf test Michal Luczaj
2025-06-11 19:56 ` [PATCH net-next v3 1/3] vsock/test: Introduce vsock_bind_try() helper Michal Luczaj
2025-06-13 15:03 ` Luigi Leonardi
2025-06-11 19:56 ` [PATCH net-next v3 2/3] vsock/test: Introduce get_transports() Michal Luczaj
2025-06-13 15:58 ` Luigi Leonardi
2025-06-17 14:12 ` Stefano Garzarella
2025-06-11 19:56 ` [PATCH net-next v3 3/3] vsock/test: Cover more CIDs in transport_uaf test Michal Luczaj
2025-06-17 14:13 ` Stefano Garzarella
2025-06-16 21:57 ` Jakub Kicinski [this message]
2025-06-17 8:25 ` [PATCH net-next v3 0/3] vsock/test: Improve " Stefano Garzarella
2025-06-17 22: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=20250616145729.1a16afdc@kernel.org \
--to=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.