Received: by 10.223.185.116 with SMTP id b49csp6007929wrg; Wed, 28 Feb 2018 02:21:07 -0800 (PST) X-Google-Smtp-Source: AH8x2272ANKb4C+bRHSwhNE0BJG3+XZsLsSGvMluXWM/0nTwGMTCp1F8XUioggwkOR7CMNaIkCS2 X-Received: by 2002:a17:902:7789:: with SMTP id o9-v6mr17814013pll.422.1519813267267; Wed, 28 Feb 2018 02:21:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519813267; cv=none; d=google.com; s=arc-20160816; b=iD71PE30ZcngNu56v+9+JikIbqkj2FFlnMLWeD+pbc2pTX0bgDIJmwY1Uhj8ohNzp3 oE8JKEROsv+CWR+Bhx+0j6z51D5uMd1CUB+eD3jI8MOdDZv8cCF0L5tEX7u0gea90CZJ X6oaeapRXJ/amA03kwPT9UH4WIVsEkyxkIlEl1v1hjhTscP7jccL2eOnP0tbimSCQ1vH tJW/1EOoBw/n+OylOw1vM6MfdFcDab/wzitJzDM9H47vvRl9CFL/cGLhRZS3VqTrxk5p 0ZZzo7JgSmfOyCcAtjjuqu5/m5wyusLFEBGn9+9LkpbO5BQmYXp5Qzd7f+k9y/O+t+X5 wU5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :arc-authentication-results; bh=YOw5B9T1Hkc8C1lofGzYH443VknXUFCYjGyAs51pC/o=; b=JY5huLbkW0pNXTOiqivigwOFa1jIB4DNBtZ9af060yzYY29i/8xqHt4Ggr0NCuD5CB Go0i9TnVwgQ3uJVRZ4YZw99eLCqalQ21Ue7fRS+YRODWn15erDwqDY3PfJnmpyUWKDG4 MtQoKPCWSlua3UpfEcW6UOYORXtKrIVUnwxxTjPt8KVVZmdmKIS64enPXf7q0ElTawV1 Ws+wMOtpCjHcNUUawCplr3ifWZQ2i2UDD+UUktrVElCq8oRQ/OTJvP+ntDy4oUjaJ7M0 ee4+WsHUY54zAsrbEoKKmjcD5aCLY26bn0Wgtzts32SHG+Zhw31BUndsPc95+qIdQ3pE aGdw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i22-v6si1052697pll.175.2018.02.28.02.20.50; Wed, 28 Feb 2018 02:21:07 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752301AbeB1KUK (ORCPT + 99 others); Wed, 28 Feb 2018 05:20:10 -0500 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:35792 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752082AbeB1KUJ (ORCPT ); Wed, 28 Feb 2018 05:20:09 -0500 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 43861A1BCB; Wed, 28 Feb 2018 10:20:09 +0000 (UTC) Received: from jason-ThinkPad-T450s.redhat.com (ovpn-12-137.pek2.redhat.com [10.72.12.137]) by smtp.corp.redhat.com (Postfix) with ESMTP id 47E802026E04; Wed, 28 Feb 2018 10:20:05 +0000 (UTC) From: Jason Wang To: mst@redhat.com, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Jason Wang Subject: [PATCH net] virtio-net: disable NAPI only when enabled during XDP set Date: Wed, 28 Feb 2018 18:20:04 +0800 Message-Id: <1519813204-10002-1-git-send-email-jasowang@redhat.com> X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Wed, 28 Feb 2018 10:20:09 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Wed, 28 Feb 2018 10:20:09 +0000 (UTC) for IP:'10.11.54.4' DOMAIN:'int-mx04.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'jasowang@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org We try to disable NAPI to prevent a single XDP TX queue being used by multiple cpus. But we don't check if device is up (NAPI is enabled), this could result stall because of infinite wait in napi_disable(). Fixing this by checking device state through netif_running() before. Fixes: 4941d472bf95b ("virtio-net: do not reset during XDP set") Signed-off-by: Jason Wang --- drivers/net/virtio_net.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c index 9bb9e56..2d54123 100644 --- a/drivers/net/virtio_net.c +++ b/drivers/net/virtio_net.c @@ -2185,8 +2185,9 @@ static int virtnet_xdp_set(struct net_device *dev, struct bpf_prog *prog, } /* Make sure NAPI is not using any XDP TX queues for RX. */ - for (i = 0; i < vi->max_queue_pairs; i++) - napi_disable(&vi->rq[i].napi); + if (netif_running(dev)) + for (i = 0; i < vi->max_queue_pairs; i++) + napi_disable(&vi->rq[i].napi); netif_set_real_num_rx_queues(dev, curr_qp + xdp_qp); err = _virtnet_set_queues(vi, curr_qp + xdp_qp); @@ -2205,7 +2206,8 @@ static int virtnet_xdp_set(struct net_device *dev, struct bpf_prog *prog, } if (old_prog) bpf_prog_put(old_prog); - virtnet_napi_enable(vi->rq[i].vq, &vi->rq[i].napi); + if (netif_running(dev)) + virtnet_napi_enable(vi->rq[i].vq, &vi->rq[i].napi); } return 0; -- 2.7.4