From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@kernel.org>
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 887A4C433F5
	for <stable@archiver.kernel.org>; Mon, 28 Mar 2022 09:48:26 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S231474AbiC1JuE (ORCPT <rfc822;stable@archiver.kernel.org>);
        Mon, 28 Mar 2022 05:50:04 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43966 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S236154AbiC1JuD (ORCPT
        <rfc822;stable@vger.kernel.org>); Mon, 28 Mar 2022 05:50:03 -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 A90141F625
        for <stable@vger.kernel.org>; Mon, 28 Mar 2022 02:48:22 -0700 (PDT)
Received: by mail-io1-f70.google.com with SMTP id q137-20020a6b8e8f000000b006495204b061so10015842iod.14
        for <stable@vger.kernel.org>; Mon, 28 Mar 2022 02:48:22 -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=voaF1O0ruJkb/Ni6djDAhe/Vm33w4JnR2Ed26i4Y+hH6A8U8zzqCD0FATtJU3Oer8J
         gRRftY+6vO0U1EjRVxnx3ySewyCkUNj4MGEbiaJVNXX5GV4PwV1abDbBau4JcqaFYhVt
         VUJbnfmOQQamX/6bgW3dZT8gUXRuuh6QIlyAQW44N+aFGqe0y085oZqidHFMonodUI48
         1qqaTbDf7Hg9NVOLc2Qjtctw5jafswWsYB7ttyKmktfuw1evh++ofIUX35Ht05g1Mz78
         rqZicSoxt1K65GS4gKNV9n8dKm07u74g9FsiRpT5C52WFWMda0L/cGAaiFbhnxwFrJYg
         eaYQ==
X-Gm-Message-State: AOAM530soPvfMfJyqlfDuMYryHhyzv96OyiFE62GNGTStRU/dHzIqwev
        ScBEd8FEoYi7E6wSiSZJxQaZEnTQ9uFqblJ0qo1kP5wwyOEG
X-Google-Smtp-Source: ABdhPJyzeX1qMoACO2pA8AueYO+lQlS5AXFOjsBz6huoRNJY9WSpaqdZ/pIq6qMIvI2Gw8vV55QNG/qPhoKV9A85R2g/iU+ap6CW
MIME-Version: 1.0
X-Received: by 2002:a05:6e02:1561:b0:2c8:3d92:ed52 with SMTP id
 k1-20020a056e02156100b002c83d92ed52mr5163039ilu.132.1648460902011; Mon, 28
 Mar 2022 02:48:22 -0700 (PDT)
Date:   Mon, 28 Mar 2022 02:48:22 -0700
In-Reply-To: <000000000000b960c00594598949@google.com>
X-Google-Appengine-App-Id: s~syzkaller
X-Google-Appengine-App-Id-Alias: syzkaller
Message-ID: <0000000000007d99f705db443685@google.com>
Subject: Re: KASAN: use-after-free Read in tc_chain_fill_node
From:   syzbot <syzbot+5f229e48cccc804062c0@syzkaller.appspotmail.com>
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: <stable.vger.kernel.org>
X-Mailing-List: stable@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.