Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp30179018rwd; Thu, 6 Jul 2023 01:59:11 -0700 (PDT) X-Google-Smtp-Source: APBJJlEQCnIIGPoX796hElInPalxDyXhQ7EQ4cYl4dNiaZtfebrTtLdfamcRPH7v6tgCDnH03j5+ X-Received: by 2002:a17:90a:fa49:b0:256:857f:823d with SMTP id dt9-20020a17090afa4900b00256857f823dmr638972pjb.48.1688633951410; Thu, 06 Jul 2023 01:59:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1688633951; cv=none; d=google.com; s=arc-20160816; b=KLZ3L+BBzFs/cHJPXp0CftOyFgAle6OAoUAD2lwrhBB0VIvv/j2COMglQ7dQLSvyGC wvHtgZuA4+p1EYasKcrD6XhStvPJRMnxHr2Jr9YJWV3tQGGa6rNWRGzQ2yhvYUVvSrBY /5mmxcG32jI9KrFxEeO7EOgEhBtKDOfjw4CCafX02iA+qjw9t3BAGiWXD+SNYq5vK3zo 64aWS0bS08iTVb26NMwZXGeb+fLnUVrlkGY9fULKR4Zd5gkgIcxN1Eiy0GiqeFXeEV/M a4MtNxPyiDZfu/j+YtF1NDbpAhG/pA1CficTOvBMcRB+lRRXqtTKanpeJ6eRxd7ZliJE 9sBg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent :content-transfer-encoding:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=u6rDF3CskNlnocyiQd+/MQFl4wcMc6bzpk2CUQ+RXxc=; fh=R5lGmkUl7G9hsufAjvARFZq8bFqQX2RUknkXOc9/Hi8=; b=NI1O+cUVQKotBF9sPeEP1BEe5okRGboCiLFUTx9Ka15RaeFic5JF8rxSoTo8KFcY8l YzzXxCqxQnU4TK3hub1R8I8xSmgUtFPkjN5d1IenSz9lu+4oScxRx9YfinfctCVM/SLg fpyLWL8m0hwolBxs5E2WRYLgwKMO5upbkbk4TUQ/jvSejfSWvnfP0exO4hi9RNpoM1ND 06TI3WjWjbGHlg7h1mdRJZZzuaIhl82U3Ggpt0KLpnqp7MF6aa8HFtaf5sQB3e7k4X+l Y5WQJVR67+GlDfRAaMgUvB6YcI2pjb8XNsjY4W7gMtlsWpxdNfXCc+/VTZm59pSGp6qr 2e7A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZWG03A+5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s2-20020a17090aba0200b00263a2156cd5si1159479pjr.30.2023.07.06.01.58.57; Thu, 06 Jul 2023 01:59:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZWG03A+5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S230321AbjGFInc (ORCPT + 99 others); Thu, 6 Jul 2023 04:43:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49842 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229489AbjGFInb (ORCPT ); Thu, 6 Jul 2023 04:43:31 -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 ESMTPS id D611D1BC8 for ; Thu, 6 Jul 2023 01:42:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1688632966; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=u6rDF3CskNlnocyiQd+/MQFl4wcMc6bzpk2CUQ+RXxc=; b=ZWG03A+5WCeYzu4Szat/i9mNdWhTRQqAMWhDGpO3Uf9D+4OUA6O0PykXJsqs7J1S4Zb/3i YggzWyF+0B831hMEP7CAdT0Q9cM3PWRe7L2ZxkUHitnCoiiLfJGGaIOJV+l/qaP7lVpZFB q+w9E8s133mVa7akD7JAYKlS8yx4ECk= Received: from mail-qk1-f200.google.com (mail-qk1-f200.google.com [209.85.222.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-54-sYMw4LyqMPydOVeO1NYiEw-1; Thu, 06 Jul 2023 04:42:44 -0400 X-MC-Unique: sYMw4LyqMPydOVeO1NYiEw-1 Received: by mail-qk1-f200.google.com with SMTP id af79cd13be357-765ad67e600so11538085a.0 for ; Thu, 06 Jul 2023 01:42:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688632964; x=1691224964; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=u6rDF3CskNlnocyiQd+/MQFl4wcMc6bzpk2CUQ+RXxc=; b=jEtArNIexIpPTXeqHQxdRVTUOiW062QAhXYY/TY1OxdYBotoXZ5j2K7L7n3UGT4hFq NJo2C1zeHCsomiIza4cqxtXRSF5HKQ72heVa3WvI6paN/UpmaJMqBRGsYMCWp5VGro55 U0pWwFoAmQtS6N5/UQ/6o3eQeWMVK975ciSMQ5PKy9dt0iJhF0mhVm0SZHHsRBsWcajU 3JqrUiCnqR0ZwvjZrx+4GOSEK4raVskWtPz7mvz4uLs+ZPGvDga4+hld8zp6meyQQPrM xkGrAnOWWZO4xOPn62nkUu0tArigg0UZOFDPckB7Cmcaq7d8SKAEMOQXzsUU5JNmgEgZ 4xmg== X-Gm-Message-State: ABy/qLZwqRkzcjCWzrtNf+j+0jY7fi8LNt8a8IeABzSyl7Nol9RgCIpR BKraiEDgLQ3NSku8wo2FjKLx6YbG6sPf9oBdTDAqNwF7i/PG7YJQTNpPMlzgxGPecTAUJpxj/49 viVoV1kbm7oHgVpyOx3i/e9M6 X-Received: by 2002:a05:620a:40c2:b0:765:9e34:a77e with SMTP id g2-20020a05620a40c200b007659e34a77emr1523541qko.2.1688632964084; Thu, 06 Jul 2023 01:42:44 -0700 (PDT) X-Received: by 2002:a05:620a:40c2:b0:765:9e34:a77e with SMTP id g2-20020a05620a40c200b007659e34a77emr1523521qko.2.1688632963710; Thu, 06 Jul 2023 01:42:43 -0700 (PDT) Received: from gerbillo.redhat.com (host-95-248-55-118.retail.telecomitalia.it. [95.248.55.118]) by smtp.gmail.com with ESMTPSA id i22-20020ae9ee16000000b00767765561absm512848qkg.100.2023.07.06.01.42.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 06 Jul 2023 01:42:43 -0700 (PDT) Message-ID: Subject: Re: [Intel-wired-lan] bug with rx-udp-gro-forwarding offloading? From: Paolo Abeni To: Ian Kumlien Cc: Alexander Lobakin , intel-wired-lan , Jakub Kicinski , Eric Dumazet , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" Date: Thu, 06 Jul 2023 10:42:38 +0200 In-Reply-To: References: <22aad588-47d6-6441-45b2-0e685ed84c8d@intel.com> <0a040331995c072c56fce58794848f5e9853c44f.camel@redhat.com> <486ae2687cd2e2624c0db1ea1f3d6ca36db15411.camel@redhat.com> <5688456234f5d15ea9ca0f000350c28610ed2639.camel@redhat.com> <92a4d42491a2c219192ae86fa04b579ea3676d8c.camel@redhat.com> <062061fc4d4d3476e3b0255803b726956686eb19.camel@redhat.com> <14cd6a50bd5de13825017b75c98cb3115e84acc1.camel@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) MIME-Version: 1.0 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2023-07-05 at 15:58 +0200, Ian Kumlien wrote: > On Wed, Jul 5, 2023 at 3:29=E2=80=AFPM Paolo Abeni wr= ote: > >=20 > > On Wed, 2023-07-05 at 13:32 +0200, Ian Kumlien wrote: > > > On Wed, Jul 5, 2023 at 12:28=E2=80=AFPM Paolo Abeni wrote: > > > >=20 > > > > On Tue, 2023-07-04 at 16:27 +0200, Ian Kumlien wrote: > > > > > More stacktraces.. =3D) > > > > >=20 > > > > > cat bug.txt | ./scripts/decode_stacktrace.sh vmlinux > > > > > [ 411.413767] ------------[ cut here ]------------ > > > > > [ 411.413792] WARNING: CPU: 9 PID: 942 at include/net/ud p.h= :509 > > > > > udpv6_queue_rcv_skb (./include/net/udp.h:509 net/ipv6/udp.c:800 > > > > > net/ipv6/udp.c:787) > > > >=20 > > > > I'm really running out of ideas here... > > > >=20 > > > > This is: > > > >=20 > > > > WARN_ON_ONCE(UDP_SKB_CB(skb)->partial_cov); > > > >=20 > > > > sort of hint skb being shared (skb->users > 1) while enqueued in > > > > multiple places (bridge local input and br forward/flood to tun > > > > device). I audited the bridge mc flooding code, and I could not fin= d > > > > how a shared skb could land into the local input path. > > > >=20 > > > > Anyway the other splats reported here and in later emails are > > > > compatible with shared skbs. > > > >=20 > > > > The above leads to another bunch of questions: > > > > * can you reproduce the issue after disabling 'rx-gro-list' on the > > > > ingress device? (while keeping 'rx-udp-gro-forwarding' on). > > >=20 > > > With rx-gro-list off, as in never turned on, everything seems to run = fine > > >=20 > > > > * do you have by chance qdiscs on top of the VM tun devices? > > >=20 > > > default qdisc is fq > >=20 > > IIRC libvirt could reset the qdisc to noqueue for the owned tun > > devices. > >=20 > > Could you please report the output of: > >=20 > > tc -d -s qdisc show dev >=20 > I don't have these set: > CONFIG_NET_SCH_INGRESS > CONFIG_NET_SCHED >=20 > so tc just gives an error... The above is confusing. AS CONFIG_NET_SCH_DEFAULT depends on CONFIG_NET_SCHED, you should not have a default qdisc, too ;) Could you please share your kernel config? Thanks! /P