From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 18A27C004D4 for ; Thu, 19 Jan 2023 11:44:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230445AbjASLoP (ORCPT ); Thu, 19 Jan 2023 06:44:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51116 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231211AbjASLnu (ORCPT ); Thu, 19 Jan 2023 06:43:50 -0500 Received: from mail-io1-f69.google.com (mail-io1-f69.google.com [209.85.166.69]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DCF902696 for ; Thu, 19 Jan 2023 03:43:25 -0800 (PST) Received: by mail-io1-f69.google.com with SMTP id k1-20020a6b3c01000000b006f744aee560so942489iob.2 for ; Thu, 19 Jan 2023 03:43:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=wBMTs/oqxa+U3Pif+UT/UzsIBETfbLQftOGnVuK+yeI=; b=ZM8c2q1XNK9oPZiL44pMLOshRHWKWUpPAEMTmtUUZHKjI35G7uiJYoTSpJM5i/B9wB KE3PTGefwbt+wi6UshwcWWRNBIhlLiABvwxhM71QQ4NcIexUCua9MBtJ730HuZJaMrlG M+2XdFOLroLPsNZ7Q/+UdGODZ8w9ys/boFDDHhvnUjQ7EPvy8JTzYpSiuYhTHvVSoTIC LYPcT2d8OSi8wjwMciQzlQkOnLSlL+6jknKnjzJmYVKAJemIWj7gs0K/ONNxJpbh7ylX 23aAJoCQy17T+QXzi5V/SHoTs4XhFImfHvWoKiIWVs4sxelN4Lu2PIT+c3g8NHa+KpeV AvUA== X-Gm-Message-State: AFqh2kplCr7++XrOuov/nvhcatEciATpKL6uReMQ8MhzLtQGCtBdvLHl fY5J/u1KwaEFGV687YckfsZ0A3PXQEk185u50WEAa+A5BBR7 X-Google-Smtp-Source: AMrXdXsXcFCp3vMPCpScL6USflrKQhOJ3FkDwUfiVyUWhU3rcEoq4fhbMsvs86VuWB6w648itUPNF4JjAkFewVI9weGat98yR27/ MIME-Version: 1.0 X-Received: by 2002:a6b:8f89:0:b0:6e2:fb39:a5d4 with SMTP id r131-20020a6b8f89000000b006e2fb39a5d4mr842130iod.45.1674128605288; Thu, 19 Jan 2023 03:43:25 -0800 (PST) Date: Thu, 19 Jan 2023 03:43:25 -0800 In-Reply-To: X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000d3a00705f29c70b6@google.com> Subject: Re: [syzbot] kernel BUG in ip_frag_next From: syzbot To: bpf@vger.kernel.org, brouer@redhat.com, davem@davemloft.net, dsahern@kernel.org, edumazet@google.com, jbrouer@redhat.com, kuba@kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, pabeni@redhat.com, saeed@kernel.org, syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org Hello, syzbot has tested the proposed patch and the reproducer did not trigger any issue: Reported-and-tested-by: syzbot+c8a2e66e37eee553c4fd@syzkaller.appspotmail.com Tested on: commit: 9ffb07a3 Merge branch 'enetc-bd-ring-cleanup' git tree: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git master console output: https://syzkaller.appspot.com/x/log.txt?x=1641e6a9480000 kernel config: https://syzkaller.appspot.com/x/.config?x=39c7bc65b36ccf9d dashboard link: https://syzkaller.appspot.com/bug?extid=c8a2e66e37eee553c4fd compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 patch: https://syzkaller.appspot.com/x/patch.diff?x=135c7f0e480000 Note: testing is done by a robot and is best-effort only.