Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp5477066ybl; Sun, 22 Dec 2019 06:59:29 -0800 (PST) X-Google-Smtp-Source: APXvYqwUorfExe8HFAnintFaJombhM/QyRgHHd+YaMNKzBbcJpT7gJ7l7rXlSbNcqPRCzRkpfJ7+ X-Received: by 2002:a9d:4e92:: with SMTP id v18mr12900876otk.47.1577026768932; Sun, 22 Dec 2019 06:59:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577026768; cv=none; d=google.com; s=arc-20160816; b=E96C0d6PqQl3fEq2bxcFrS9FK6pXZJRKDRXa15scepVQGqOEQ+1/aREV+nUvXFQH+F i5FEpbV1Z5i2ixTBmYxj3OjCnY+GQRIM0b4RgGBujBYqVhZD98xZIPr5Jsto0D/u4Bsm AY0/iLmUX5MnzeZtySn5pMsixzssIESoV9JrDgBbxKMkqZA37i+siamUQf7esLyLHetC HMNbiaDkrl7Lilp/UKLyoZOlQ5u2tJ2tkl3GLEDNqNRB/9i5bQj85MoRINagvga0b1SB jre4z9yriHIies1Jw+epLO5gMXRJzy4ky0VLaMHJYsOtpYh3MaO2GFFMIVlAAGINspsz jdyQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=e63r31MTLSpTW749sLIQEcCg9+hahBZpdCxIHQv87Ww=; b=De8v2ZUCKieweXSb5yy5jmRdkVot2TVr2KUpREl0Dj4bpwMyb5zbZrwhRurcxDrzzH uNvUjbXv7mj6EcB3/ePz8OuiGdgriqPB1uf3WK/l9bEE1rdjCh3IKxmb7+dLeQsSogzl VC6Q0Zhr7WCeVmEl8SVTXMqjuf9WqVt14yNroQkxmlnPUxTLP6IY8iE9Kg/c/Taczwrh fZoSDLTzmG+HOwT9yeQFjoL7wh5AxkRZVYmGroAcLIrw278iqPzwHlcioQBqlgel/8vY TWXxZmY+AEPDOTLmGSWqBpRAv1mmGONN2bB2VJLvm9RJUdnFHgtfVDEHzOg4bkQQ6DrC 7p5A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=bAAHA3no; 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=pass (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 e20si8060951oig.199.2019.12.22.06.59.13; Sun, 22 Dec 2019 06:59:28 -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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=bAAHA3no; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726539AbfLVO5y (ORCPT + 99 others); Sun, 22 Dec 2019 09:57:54 -0500 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:21984 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725997AbfLVO5y (ORCPT ); Sun, 22 Dec 2019 09:57:54 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1577026672; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=e63r31MTLSpTW749sLIQEcCg9+hahBZpdCxIHQv87Ww=; b=bAAHA3nog0SyCgoSjSYt6a0XkV/RUAQMsUQTgUqyPmAZhu1KlDB4lY7ajINFqwdO+wA2Bi WKRlSMvEukUiHyo4oX8I5YRGQPZifuKp2cYaOqRuFXnba4UeuLSt8zeZ7Vr88+icNIBnrX cHIBHs/QnJgwi5c+fLPeI4gYMIbpsQ4= Received: from mail-qk1-f199.google.com (mail-qk1-f199.google.com [209.85.222.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-188-ZdsbIXF2Mh2fyg-FQQdf9A-1; Sun, 22 Dec 2019 09:57:49 -0500 X-MC-Unique: ZdsbIXF2Mh2fyg-FQQdf9A-1 Received: by mail-qk1-f199.google.com with SMTP id k10so4301146qki.2 for ; Sun, 22 Dec 2019 06:57:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=e63r31MTLSpTW749sLIQEcCg9+hahBZpdCxIHQv87Ww=; b=M2Pmqj61a3iU/gi0HgI+4Xzo/TQwZUH8gXTJjXuKQ/J7R2Dy17nNB31cW7TwDMxjJF pIiysDJrEyt4vtH6q46TPWuHKfccMN1ZcugBbei269fFELsVItxgNJPr9mLoM6XcSmzJ Uv6dBN1Y60QrxV/nFO5CGVvcExFit0xiIiZ2FtkM2WwWojKEQ5NIRUdIGqdEJa9YvjWS +LOORDobsr6ZOrgheIs/hz0T802NxdJT2WN+EV4G6LWvI8ujRC7QqQdTzJdl9tT7nUyL MUbsuAOVhm5vc6VHN2akHPyrI0shm4j+n6zvR2uVvMUCpkStgh1FpaMFssBKenF0e5Ls jPQg== X-Gm-Message-State: APjAAAVuLoOQ4dlsCNgze8c0LW+y0jjF2+UHBHhF5OHaWFxT82+Pdd/S mGx9Kty/XHinLQX4YhAHd2jy4yWyTOcAz76hhlmwLgIwkHabZ3bAQUCFKFmyGjQb1Q3nOs97yQ8 W6x3UuK1BDFnVRSQhrkG/dvKI X-Received: by 2002:a37:bf82:: with SMTP id p124mr22638138qkf.337.1577026667437; Sun, 22 Dec 2019 06:57:47 -0800 (PST) X-Received: by 2002:a37:bf82:: with SMTP id p124mr22638124qkf.337.1577026667107; Sun, 22 Dec 2019 06:57:47 -0800 (PST) Received: from redhat.com (bzq-79-181-48-215.red.bezeqint.net. [79.181.48.215]) by smtp.gmail.com with ESMTPSA id k22sm4907268qkg.80.2019.12.22.06.57.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 22 Dec 2019 06:57:46 -0800 (PST) Date: Sun, 22 Dec 2019 09:57:40 -0500 From: "Michael S. Tsirkin" To: Willem de Bruijn Cc: Alistair Delva , Network Development , stable , Jason Wang , "David S . Miller" , kernel-team@android.com, virtualization@lists.linux-foundation.org, linux-kernel Subject: Re: [PATCH net] virtio-net: Skip set_features on non-cvq devices Message-ID: <20191222095141-mutt-send-email-mst@kernel.org> References: <20191220212207.76726-1-adelva@google.com> <20191222080754-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Dec 22, 2019 at 09:21:43AM -0500, Willem de Bruijn wrote: > On Sun, Dec 22, 2019 at 8:11 AM Michael S. Tsirkin wrote: > > > > On Fri, Dec 20, 2019 at 10:08:41PM -0500, Willem de Bruijn wrote: > > > On Fri, Dec 20, 2019 at 4:22 PM Alistair Delva wrote: > > > > > > > > On devices without control virtqueue support, such as the virtio_net > > > > implementation in crosvm[1], attempting to configure LRO will panic the > > > > kernel: > > > > > > > > kernel BUG at drivers/net/virtio_net.c:1591! > > > > invalid opcode: 0000 [#1] PREEMPT SMP PTI > > > > CPU: 1 PID: 483 Comm: Binder:330_1 Not tainted 5.4.5-01326-g19463e9acaac #1 > > > > Hardware name: ChromiumOS crosvm, BIOS 0 > > > > RIP: 0010:virtnet_send_command+0x15d/0x170 [virtio_net] > > > > Code: d8 00 00 00 80 78 02 00 0f 94 c0 65 48 8b 0c 25 28 00 00 00 48 3b 4c 24 70 75 11 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 <0f> 0b e8 ec a4 12 c8 66 90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 > > > > RSP: 0018:ffffb97940e7bb50 EFLAGS: 00010246 > > > > RAX: ffffffffc0596020 RBX: ffffa0e1fc8ea840 RCX: 0000000000000017 > > > > RDX: ffffffffc0596110 RSI: 0000000000000011 RDI: 000000000000000d > > > > RBP: ffffb97940e7bbf8 R08: ffffa0e1fc8ea0b0 R09: ffffa0e1fc8ea0b0 > > > > R10: ffffffffffffffff R11: ffffffffc0590940 R12: 0000000000000005 > > > > R13: ffffa0e1ffad2c00 R14: ffffb97940e7bc08 R15: 0000000000000000 > > > > FS: 0000000000000000(0000) GS:ffffa0e1fd100000(006b) knlGS:00000000e5ef7494 > > > > CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 > > > > CR2: 00000000e5eeb82c CR3: 0000000079b06001 CR4: 0000000000360ee0 > > > > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > > > > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > > > > Call Trace: > > > > ? preempt_count_add+0x58/0xb0 > > > > ? _raw_spin_lock_irqsave+0x36/0x70 > > > > ? _raw_spin_unlock_irqrestore+0x1a/0x40 > > > > ? __wake_up+0x70/0x190 > > > > virtnet_set_features+0x90/0xf0 [virtio_net] > > > > __netdev_update_features+0x271/0x980 > > > > ? nlmsg_notify+0x5b/0xa0 > > > > dev_disable_lro+0x2b/0x190 > > > > ? inet_netconf_notify_devconf+0xe2/0x120 > > > > devinet_sysctl_forward+0x176/0x1e0 > > > > proc_sys_call_handler+0x1f0/0x250 > > > > proc_sys_write+0xf/0x20 > > > > __vfs_write+0x3e/0x190 > > > > ? __sb_start_write+0x6d/0xd0 > > > > vfs_write+0xd3/0x190 > > > > ksys_write+0x68/0xd0 > > > > __ia32_sys_write+0x14/0x20 > > > > do_fast_syscall_32+0x86/0xe0 > > > > entry_SYSENTER_compat+0x7c/0x8e > > > > > > > > This happens because virtio_set_features() does not check the presence > > > > of the control virtqueue feature, which is sanity checked by a BUG_ON > > > > in virtnet_send_command(). > > > > > > > > Fix this by skipping any feature processing if the control virtqueue is > > > > missing. This should be OK for any future feature that is added, as > > > > presumably all of them would require control virtqueue support to notify > > > > the endpoint that offload etc. should begin. > > > > > > > > [1] https://chromium.googlesource.com/chromiumos/platform/crosvm/ > > > > > > > > Fixes: a02e8964eaf9 ("virtio-net: ethtool configurable LRO") > > > > Cc: stable@vger.kernel.org [4.20+] > > > > Cc: Michael S. Tsirkin > > > > Cc: Jason Wang > > > > Cc: David S. Miller > > > > Cc: kernel-team@android.com > > > > Cc: virtualization@lists.linux-foundation.org > > > > Cc: linux-kernel@vger.kernel.org > > > > Signed-off-by: Alistair Delva > > > > > > Thanks for debugging this, Alistair. > > > > > > > --- > > > > drivers/net/virtio_net.c | 3 +++ > > > > 1 file changed, 3 insertions(+) > > > > > > > > diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c > > > > index 4d7d5434cc5d..709bcd34e485 100644 > > > > --- a/drivers/net/virtio_net.c > > > > +++ b/drivers/net/virtio_net.c > > > > @@ -2560,6 +2560,9 @@ static int virtnet_set_features(struct net_device *dev, > > > > u64 offloads; > > > > int err; > > > > > > > > + if (!vi->has_cvq) > > > > + return 0; > > > > + > > > > > > Instead of checking for this in virtnet_set_features, how about we > > > make configurability contingent on cvq in virtnet_probe: > > > > > > - if (virtio_has_feature(vdev, VIRTIO_NET_F_CTRL_GUEST_OFFLOADS)) > > > + if (virtio_has_feature(vdev, VIRTIO_NET_F_CTRL_GUEST_OFFLOADS) && > > > + virtio_has_feature(vdev, VIRTIO_NET_F_CTRL_VQ)) > > > dev->hw_features |= NETIF_F_LRO; > > > > > > Based on this logic a little below in the same function > > > > > > if (virtio_has_feature(vdev, VIRTIO_NET_F_CTRL_VQ)) > > > vi->has_cvq = true; > > > > > > This would be a regression on old hypervisors which didn't have > > CTL VQ - suddenly they will lose offloads. > > dev->features still correctly displays whether offloads are enabled. > Removing it from dev->hw_features just renders it non-configurable. Oh you are right. I confused it with dev->features. > Note that before the patch that is being fixed the offloads were > enabled, but ethtool would show them as off. So the bug is in spec, it should have said VIRTIO_NET_F_CTRL_GUEST_OFFLOADS depends on VIRTIO_NET_F_CTRL_VQ, but we missed that part. We can and I guess should add this as a recommendation but it's too late to make it a MUST. Meanwhile I would say it's cleanest to work around this in virtnet_validate by clearing VIRTIO_NET_F_CTRL_GUEST_OFFLOADS if VIRTIO_NET_F_CTRL_VQ is off, with a big comment explaining it's a spec bug. -- MST