All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: virtualization@lists.linux.dev
Cc: netdev@vger.kernel.org, Stefano Garzarella <sgarzare@redhat.com>,
	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: [RFC] loading vmw_vsock_virtio_transport by systemd breaks vsock_loopback autoloading
Date: Fri, 20 Mar 2026 12:02:24 +0100	[thread overview]
Message-ID: <20260320110224.GA140154@pevik> (raw)

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.

Kind regards,
Petr

[1] https://github.com/systemd/systemd/issues/41100
[2] https://bugzilla.suse.com/attachment.cgi?id=888729
[3] https://github.com/systemd/systemd/issues/41100#issuecomment-4056603242

             reply	other threads:[~2026-03-20 11:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 11:02 Petr Vorel [this message]
2026-03-30 14:46 ` [RFC] loading vmw_vsock_virtio_transport by systemd breaks vsock_loopback autoloading Stefano Garzarella
2026-03-30 23:09   ` [LTP] " Petr Vorel
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=20260320110224.GA140154@pevik \
    --to=pvorel@suse.cz \
    --cc=arvidjaar@gmail.com \
    --cc=bluca@debian.org \
    --cc=luca.boccassi@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --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 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.