Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp4521509pxb; Thu, 14 Oct 2021 06:54:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJypYj7LNhVGiHGxWy3FfzecVM2yeMUvKAZAUQa06sBNbiluwSQ+ESvzB6zsBLV8AbGWDY6a X-Received: by 2002:a17:906:35cc:: with SMTP id p12mr4056901ejb.351.1634219695244; Thu, 14 Oct 2021 06:54:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634219695; cv=none; d=google.com; s=arc-20160816; b=AvcvoM1vn9g9Qp22lhsT/gpgDRWDk6TmJNVJMpU4XH+k8gEDJLgW8t69Jr+ChSBbav mv5HSz1we0zkvK4BqtTh9LOSgu3dSffqKgzL09x4xdE5k8EW+wvRNKpf73R/ICDqMS5F fn/2kfBLg9fe93vooq4fqBaSmhH4LKH3VwIoORYrEKXbJJaTQYwBQDgVsOcPNqbEafMi 8qOmzPrylM7Ks37nQIT0t4+6gJDpV0qlXwDEo/zAIrzCnc3q4ca0z19jWCHuDNuJppqG +385Es1rmmEXUE7Y6hz/WOj2ypK8s2kAkTzuSAOFArRzxnJX03qXSX8pVApgkg82Akr/ 3zMw== 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:date:cc:to:from:subject :message-id:dkim-signature; bh=NU91yXOcSHE5nSjfMfHje2UOd8qpOzLy0LtZp6G93T4=; b=hIzFaWyEBpr5z8LJNsoLZ1QfqWzdLr2cboD9B9pKY8hNlb56vpWQ/z17h9IJp8zWQD bIdCY1UroNEB7SabiDJ0sRrkySnQkPIg/6CTGzi7rUnwkxvNOksnANXNy05SSNUPzfZj kJz6OdiPvOoLnu4SwceDrpamG4sDxR+ed5ElQA0YnuWOdUgV98kC2UyssKUyc15smaKY AdVXfZfe3gyYShRVpcWo07l5QSEgAYj85vYetaCkuSkLCcmElNRN+NFRINbFVjKwtTAT 03AgVV3DtrpF79Tmr4uRuNcLbmkKMhQ0+ddeN28N+L+WZFZ3uTYh8eLSmPPgCO3Qagl5 Pbxg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=AB7UPs+r; 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b12si5940538edd.530.2021.10.14.06.54.30; Thu, 14 Oct 2021 06:54:55 -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=@redhat.com header.s=mimecast20190719 header.b=AB7UPs+r; 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230177AbhJNNwL (ORCPT + 99 others); Thu, 14 Oct 2021 09:52:11 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:57969 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231365AbhJNNwK (ORCPT ); Thu, 14 Oct 2021 09:52:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1634219405; 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=NU91yXOcSHE5nSjfMfHje2UOd8qpOzLy0LtZp6G93T4=; b=AB7UPs+rwgz2HBsB7WXnX64N2G94HOQEFlbiv2xdh0pSneXqstNHEJYHssiJUkKnCVOo/6 SMjvvX90RDakNCd1GX1lgIuVf82iQH9kzs5WTYSvrQOgEBuD6O0TsYenKSZHMY6i/mwfPj TK+4DCysQGNTK9voqG+VzKLuDJMYOXY= Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-594-EjE6mZnFNPqeTq_QjYtjQQ-1; Thu, 14 Oct 2021 09:50:03 -0400 X-MC-Unique: EjE6mZnFNPqeTq_QjYtjQQ-1 Received: by mail-wr1-f72.google.com with SMTP id r21-20020adfa155000000b001608162e16dso4579387wrr.15 for ; Thu, 14 Oct 2021 06:50:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=NU91yXOcSHE5nSjfMfHje2UOd8qpOzLy0LtZp6G93T4=; b=wJS6/uzIaNwJYA+NhCaBEUyIYcVdettPVk1yPabilasqGymZT+D3DAALqJRuM6N2Y5 yV3lN5OxZtAoP8GxSAlaNRnRniTHMz5+yFWJFcnfaNZ2epVEpRAlU85puK1NPL5QHGpJ BDRkJgU0iHOUKFGM0+v9gXoLRanNaaoTf68bnhIGTy3TDYPqHVGVS/boS8q6MwnAN1Nn vXDogTcFVhJ//lRihn9uhmJgDawsqJske7ZO/Vg4wFxad3NzuWhvif06EW9Zbb74KN6Y eHZYy9TtZzF3jvtyzhhVp4eMxh5cpE2f4TcDc6sjwS6NIhsiWcCC4CjuDXa3Jnvk0M2c bACA== X-Gm-Message-State: AOAM53188+PL92NvVpCqI0Za40Wg15Cu1ElpMnhdX3CAa5e6+2kctWRm gys/JwT9Yw/7X2N9lFaHfgkEwQbBuSuTHcLX4IuVm2CkYSoHv9DwdSUUNBrM/yDSindlD+4RrXQ TwNlbhwPsyyedzjfA5EHvfkGF X-Received: by 2002:adf:a48c:: with SMTP id g12mr6772220wrb.341.1634219402592; Thu, 14 Oct 2021 06:50:02 -0700 (PDT) X-Received: by 2002:adf:a48c:: with SMTP id g12mr6772182wrb.341.1634219402382; Thu, 14 Oct 2021 06:50:02 -0700 (PDT) Received: from gerbillo.redhat.com (146-241-231-16.dyn.eolo.it. [146.241.231.16]) by smtp.gmail.com with ESMTPSA id c15sm2496966wrs.19.2021.10.14.06.50.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 14 Oct 2021 06:50:02 -0700 (PDT) Message-ID: Subject: Re: [syzbot] BUG: corrupted list in netif_napi_add From: Paolo Abeni To: Daniel Borkmann , syzbot , andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org, davem@davemloft.net, hawk@kernel.org, john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org, kuba@kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, songliubraving@fb.com, syzkaller-bugs@googlegroups.com, yhs@fb.com Cc: toke@toke.dk, joamaki@gmail.com Date: Thu, 14 Oct 2021 15:50:00 +0200 In-Reply-To: References: <0000000000005639cd05ce3a6d4d@google.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2021-10-13 at 15:35 +0200, Daniel Borkmann wrote: > On 10/13/21 1:40 PM, syzbot wrote: > > Hello, > > > > syzbot found the following issue on: > > [ +Paolo/Toke wrt veth/XDP, +Jussi wrt bond/XDP, please take a look, thanks! ] For the records: Toke and me are actively investigating this issue and the other recent related one. So far we could not find anything relevant. The onluy note is that the reproducer is not extremelly reliable - I could not reproduce locally, and multiple syzbot runs on the same code give different results. Anyhow, so far the issue was only observerable on a specific 'next' commit which is currently "not reachable" from any branch. I'm wondering if the issue was caused by some incosistent status of such tree. Cheers, Paolo