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 D471FC433EF for ; Mon, 20 Jun 2022 09:53:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240363AbiFTJxa (ORCPT ); Mon, 20 Jun 2022 05:53:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55524 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240520AbiFTJxS (ORCPT ); Mon, 20 Jun 2022 05:53:18 -0400 Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 011E313E0A for ; Mon, 20 Jun 2022 02:53:17 -0700 (PDT) Received: by mail-io1-f70.google.com with SMTP id l7-20020a6b7007000000b00669b2a0d497so5886951ioc.0 for ; Mon, 20 Jun 2022 02:53:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:date:in-reply-to:message-id:subject :from:to; bh=sVvRetvU66viZg03zt42J481swUWQOVgkFgrLPfYY/8=; b=8JGZ8yVGyboTezioSluMTbHnTqiQ2vxE7GMERtM0Di+NHFbMc5FLUfBmkKReU0+Dm3 1Bd/2/6HmWa/HsD46ur9c30NLfG8RVAhxfNRnUY4j8V4toY+eYk8Uygage+1e4wF197z pbdww0ZzlxB3/cgK35R1Efjflb8pxDBS8OrDl+Rard0U3rHH4JlxYJzCs9sDQo8od34+ ya/fQQodDm2fv7y0FPeXVJL3Zf96nyBP9k/JK8WSqnYX9d6gOJFJQ7te+B1jkbA+naD4 dm3iwrBzvsESVRP/e3mSnCXpRFhhJhdEz7YpLTPvWZTlG09ueoK3j/fyuSjVfdpS4kzR hwrQ== X-Gm-Message-State: AJIora8kKSqTpH8LXXjU1zM2ASNc5ewBvsmmXXn5HCuINs+t/BnqwkgN L0p4/urhZ80x5WDYYqAhBUfwcn/lqjjAluFUa9qmpC5MsjvZ X-Google-Smtp-Source: AGRyM1vNey1loZwui/9Tq4aWwQQLOriKBW5i8qao0kEqs7NYzyrA4LorjllZjbLpixAZkKEO66/vWR9A9eXPcRJkU41H3fEiqgUD MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1ba3:b0:2d8:d74b:8ff6 with SMTP id n3-20020a056e021ba300b002d8d74b8ff6mr10483467ili.264.1655718796419; Mon, 20 Jun 2022 02:53:16 -0700 (PDT) Date: Mon, 20 Jun 2022 02:53:16 -0700 In-Reply-To: <000000000000b960c00594598949@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000b5681705e1de1219@google.com> Subject: Re: KASAN: use-after-free Read in tc_chain_fill_node From: syzbot To: davem@davemloft.net, gregkh@linuxfoundation.org, jiri@mellanox.com, lee.jones@linaro.org, linux-kernel@vger.kernel.org, stable-commits@vger.kernel.org, stable@vger.kernel.org, syzkaller-lts-bugs@googlegroups.com, vladbu@mellanox.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This bug is marked as fixed by commit: net: core: netlink: add helper refcount dec and lock function net: sched: add helper function to take reference to Qdisc net: sched: extend Qdisc with rcu net: sched: rename qdisc_destroy() to qdisc_put() net: sched: use Qdisc rcu API instead of relying on rtnl lock But I can't find it in any tested tree for more than 90 days. Is it a correct commit? Please update it by replying: #syz fix: exact-commit-title Until then the bug is still considered open and new crashes with the same signature are ignored.