Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp3889910pxv; Mon, 19 Jul 2021 11:12:53 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwGZqbC8i052bId3NNshMi0p5WL3rohBAtQMdNxWHBNQ19FAKCwiP1pqAX/pNbSXWRxLZCL X-Received: by 2002:a92:6809:: with SMTP id d9mr18024663ilc.107.1626718282670; Mon, 19 Jul 2021 11:11:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626718282; cv=none; d=google.com; s=arc-20160816; b=CeCN+HCGKIVtAh+vpI6LyQ448jW3jJeS+0UmUSvD+pD/TOnzxPuJfoC1v/HirHv7/W OaiMEzOojjKV9A02DnlrjIWR1vJTDTnfWFq5EaEWcv2B3iwT7DqMFDVVPPfct8BfJ+8K niD2v2k4eg95HIf3leZgijCg51lgcT/xRYgVNUSttsStTnllFkteWSDf750reOStvWL+ xz9S/Y2zOWnQNcc5WhiUH1V9u00uP481La1WOoNNz0HmJ9sa8XyClcApd9ur8jDs3EIv kQPfygxUfIMSQg5L2W7OuinbYZi8G2Urajfldc7ADP1ZjPU6x9dFLNKn50AiJoHGFdux rTRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=4LmXaZ7ZtevkTQfJxcbYFSo3tpmSkbaIjzh+hRECIZo=; b=VHa5wOVnPMiBGc1qFa2tB+uIdoaC/NogY3rhnexKav1qDJeh6zrIOmGVo5e2CWDtiK CpWTXwcyzqbO8psihxZP+CjSi83bakXPTDu43p7wsZp12LBfe1x+dmyXN5va/3lcAtN+ gjfHjyQxMDd78L820pMWSwX9Wz2vhQ53eEZoqUIOWWaUwL6A5Wx3ri7PwAeuK2PoJ9k+ NowzcWb+caerU2aFmXiS649uamUQ4/ZXb4jqEFQgN4xQAZ6s5PCIbiRIcztVS1WfWsHx vQoPlYeEa0GWmOzE59vTkiWXjbH4InsO1c+YcJa9dTtmLVkpuMqwHw8CUSZ6d4K0dKlK nYrg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=mUwD6WRD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s13si21281222ilp.102.2021.07.19.11.11.10; Mon, 19 Jul 2021 11:11:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=mUwD6WRD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348181AbhGSR2Q (ORCPT + 99 others); Mon, 19 Jul 2021 13:28:16 -0400 Received: from mail.kernel.org ([198.145.29.99]:47370 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1349595AbhGSPqA (ORCPT ); Mon, 19 Jul 2021 11:46:00 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 81FE660C40; Mon, 19 Jul 2021 16:26:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626711999; bh=1JeBbGZn+BiNrwShiuCz03E6c59y9rfGeaGc6IClWw8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=mUwD6WRDm3njLoKRpPDplWzUJHFEN0wDc71gLg+owEuinBO8UhuBTZ+fhsfvq+jnq 6oXsBeJ7z44GxL50Z5TvmQ2qj0+Nri/NVFBTf0cQgVg7VFTR64keim3HVVinBKpkRk SqgJBGWpTYH3awP6E8T83SQJK3IA4ku7Mz9F56ts= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, "Michael S. Tsirkin" , Sasha Levin Subject: [PATCH 5.12 211/292] virtio_net: move tx vq operation under tx queue lock Date: Mon, 19 Jul 2021 16:54:33 +0200 Message-Id: <20210719144949.935298466@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210719144942.514164272@linuxfoundation.org> References: <20210719144942.514164272@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Michael S. Tsirkin [ Upstream commit 5a2f966d0f3fa0ef6dada7ab9eda74cacee96b8a ] It's unsafe to operate a vq from multiple threads. Unfortunately this is exactly what we do when invoking clean tx poll from rx napi. Same happens with napi-tx even without the opportunistic cleaning from the receive interrupt: that races with processing the vq in start_xmit. As a fix move everything that deals with the vq to under tx lock. Fixes: b92f1e6751a6 ("virtio-net: transmit napi") Signed-off-by: Michael S. Tsirkin Signed-off-by: Sasha Levin --- drivers/net/virtio_net.c | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c index db9a876035ec..beb086023093 100644 --- a/drivers/net/virtio_net.c +++ b/drivers/net/virtio_net.c @@ -1514,6 +1514,8 @@ static int virtnet_poll_tx(struct napi_struct *napi, int budget) struct virtnet_info *vi = sq->vq->vdev->priv; unsigned int index = vq2txq(sq->vq); struct netdev_queue *txq; + int opaque; + bool done; if (unlikely(is_xdp_raw_buffer_queue(vi, index))) { /* We don't need to enable cb for XDP */ @@ -1523,10 +1525,28 @@ static int virtnet_poll_tx(struct napi_struct *napi, int budget) txq = netdev_get_tx_queue(vi->dev, index); __netif_tx_lock(txq, raw_smp_processor_id()); + virtqueue_disable_cb(sq->vq); free_old_xmit_skbs(sq, true); + + opaque = virtqueue_enable_cb_prepare(sq->vq); + + done = napi_complete_done(napi, 0); + + if (!done) + virtqueue_disable_cb(sq->vq); + __netif_tx_unlock(txq); - virtqueue_napi_complete(napi, sq->vq, 0); + if (done) { + if (unlikely(virtqueue_poll(sq->vq, opaque))) { + if (napi_schedule_prep(napi)) { + __netif_tx_lock(txq, raw_smp_processor_id()); + virtqueue_disable_cb(sq->vq); + __netif_tx_unlock(txq); + __napi_schedule(napi); + } + } + } if (sq->vq->num_free >= 2 + MAX_SKB_FRAGS) netif_tx_wake_queue(txq); -- 2.30.2