From nobody Mon Jun 22 14:26:16 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 304A1C433F5 for ; Tue, 22 Mar 2022 10:38:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233139AbiCVKkM (ORCPT ); Tue, 22 Mar 2022 06:40:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55304 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233109AbiCVKkJ (ORCPT ); Tue, 22 Mar 2022 06:40:09 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 109D15AA5A for ; Tue, 22 Mar 2022 03:38:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1647945515; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=VkoZGCDazaob935cf0K6/xqwp1grV8y7vA1EUagsdw8=; b=NccPzVcc4DhwBJ1XjV1y7PXaSq9M/aKVd/b06/x4Bn/ivTykxUpfVf0h9sovnkF+/DoXNd l09B/NIeckA8YgU9vnVEvKMudxoNZnCDqHhdybyR9Flvw3LOHl8t1q/OHW9B0ZL+j2ulV0 NL5LWitXoQY0Fs2cqGbDLS/dLISrFtM= Received: from mail-qk1-f198.google.com (mail-qk1-f198.google.com [209.85.222.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-442-mNcO7qJjPr2sofAqm7Ln7g-1; Tue, 22 Mar 2022 06:38:34 -0400 X-MC-Unique: mNcO7qJjPr2sofAqm7Ln7g-1 Received: by mail-qk1-f198.google.com with SMTP id b133-20020a37678b000000b0067d24942b91so11475468qkc.12 for ; Tue, 22 Mar 2022 03:38:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=VkoZGCDazaob935cf0K6/xqwp1grV8y7vA1EUagsdw8=; b=RCZf/ltKyspiwurUXtXpQRLz9mtILgpzZc/pgwZlMikZCPjpWxEf+OJYVuQRPdEuDg u2RdJk6szvWNM9PxHStKhg85ZUY9BaWzRDd0uS3/h5393Xj9mFN2164sIDqKCVA7kK9b m1IHSH6w1z/ELuza3Wt58dbbhV4wtfuoiS7EX1LbfvfjL8fB4f+dyonp46D8Uk+d6HvO 56UfiO2jt2u69zknD7xhwB5OrWphB/4hEU1Bv0qAJ769v6F8bkUxNq0AoEZY6dUUY8vf cCE/b8rxj4QParfP2kPl/CnZsz3q41WSA7Qwg4iVfZVSoHHBYP400CpnpzwbgP48fXxl GLog== X-Gm-Message-State: AOAM5334vyjqU+pDlgeY7oFPkFlCP5gKwLWHYpSNLanM5CsX4cg1gr3v tftp9P0zY2gDoZtIc4f19XmK1mn3Cg1Cb9uKeQZU2oHZWzpNAFD4/NiZowa28ymyIuGBTEKE837 SFblKPhmnjcC5fzghlujnBrRf X-Received: by 2002:a05:6214:29ca:b0:441:1f8c:e58d with SMTP id gh10-20020a05621429ca00b004411f8ce58dmr7306560qvb.111.1647945514089; Tue, 22 Mar 2022 03:38:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz4XnbEotBgwmm8Kokd0VkMAvlrSAfcDAHK9dNDeWtrOWpekkIQX4QyQevtVagOHVlC3sFqKg== X-Received: by 2002:a05:6214:29ca:b0:441:1f8c:e58d with SMTP id gh10-20020a05621429ca00b004411f8ce58dmr7306547qvb.111.1647945513838; Tue, 22 Mar 2022 03:38:33 -0700 (PDT) Received: from step1.redhat.com ([87.12.25.114]) by smtp.gmail.com with ESMTPSA id q123-20020a378e81000000b0067eb3d6f605sm1532443qkd.0.2022.03.22.03.38.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Mar 2022 03:38:33 -0700 (PDT) From: Stefano Garzarella To: netdev@vger.kernel.org Cc: virtualization@lists.linux-foundation.org, Stefano Garzarella , Asias He , "David S. Miller" , Jakub Kicinski , Stefan Hajnoczi , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Paolo Abeni , "Michael S. Tsirkin" Subject: [PATCH net] vsock/virtio: enable VQs early on probe Date: Tue, 22 Mar 2022 11:38:23 +0100 Message-Id: <20220322103823.83411-1-sgarzare@redhat.com> X-Mailer: git-send-email 2.35.1 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" virtio spec requires drivers to set DRIVER_OK before using VQs. This is set automatically after probe returns, but virtio-vsock driver uses VQs in the probe function to fill rx and event VQs with new buffers. Let's fix this, calling virtio_device_ready() before using VQs in the probe function. Fixes: 0ea9e1d3a9e3 ("VSOCK: Introduce virtio_transport.ko") Signed-off-by: Stefano Garzarella --- net/vmw_vsock/virtio_transport.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/net/vmw_vsock/virtio_transport.c b/net/vmw_vsock/virtio_transp= ort.c index 5afc194a58bb..b1962f8cd502 100644 --- a/net/vmw_vsock/virtio_transport.c +++ b/net/vmw_vsock/virtio_transport.c @@ -622,6 +622,8 @@ static int virtio_vsock_probe(struct virtio_device *vde= v) INIT_WORK(&vsock->event_work, virtio_transport_event_work); INIT_WORK(&vsock->send_pkt_work, virtio_transport_send_pkt_work); =20 + virtio_device_ready(vdev); + mutex_lock(&vsock->tx_lock); vsock->tx_run =3D true; mutex_unlock(&vsock->tx_lock); --=20 2.35.1