From: Stefano Garzarella <sgarzare@redhat.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: virtualization@lists.linux.dev, netdev@vger.kernel.org,
Valentin Lefebvre <valentin.lefebvre@suse.com>,
Yu Watanabe <watanabe.yu@gmail.com>,
Andrei Borzenkov <arvidjaar@gmail.com>,
Luca Boccassi <luca.boccassi@gmail.com>,
Luca Boccassi <bluca@debian.org>
Subject: Re: [RFC] loading vmw_vsock_virtio_transport by systemd breaks vsock_loopback autoloading
Date: Mon, 30 Mar 2026 16:46:24 +0200 [thread overview]
Message-ID: <acqLo6-IQVBzY3UW@sgarzare-redhat> (raw)
In-Reply-To: <20260320110224.GA140154@pevik>
On Fri, Mar 20, 2026 at 12:02:24PM +0100, Petr Vorel wrote:
>Hi all,
>
>there is a systemd bug [1] which causes vsock_loopback not to be autoloaded due
>previous loading vmw_vsock_virtio_transport in an early phase of boot.
>vmw_vsock_virtio_transport requires vmw_vsock_virtio_transport_common and vsock,
>vsock_loopback requires vsock.
>
>Reproducer: [2].
>Proposed fix in systemd: [3]
>
>While I think the bug should be fixed in systemd with proposed fix [3] we'd like
>to know opinion of the kernel vsock developers in case there is a way to improve
>vsock modules autoloading.
The original idea of vsock_loopback was to be used just for
testing/debugging, so maybe even the autoloading when no other transport
was loaded wasn't a great idea, but at the time we thought it might be
useful for testing.
In general, therefore, if you want to use the loopback, it's always best
to load vsock_loopback.
What use case is being affected by the fact that vsock_loopback isn't
loaded automatically?
Thanks,
Stefano
next prev parent reply other threads:[~2026-03-30 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 11:02 [RFC] loading vmw_vsock_virtio_transport by systemd breaks vsock_loopback autoloading Petr Vorel
2026-03-30 14:46 ` Stefano Garzarella [this message]
2026-03-30 23:09 ` Petr Vorel
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=acqLo6-IQVBzY3UW@sgarzare-redhat \
--to=sgarzare@redhat.com \
--cc=arvidjaar@gmail.com \
--cc=bluca@debian.org \
--cc=luca.boccassi@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=valentin.lefebvre@suse.com \
--cc=virtualization@lists.linux.dev \
--cc=watanabe.yu@gmail.com \
/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