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 3F500C43334
	for <stable@archiver.kernel.org>; Mon, 20 Jun 2022 09:53:30 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S239886AbiFTJx3 (ORCPT <rfc822;stable@archiver.kernel.org>);
        Mon, 20 Jun 2022 05:53:29 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55526 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S240528AbiFTJxS (ORCPT
        <rfc822;stable@vger.kernel.org>); Mon, 20 Jun 2022 05:53:18 -0400
Received: from mail-il1-f200.google.com (mail-il1-f200.google.com [209.85.166.200])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0786B13E26
        for <stable@vger.kernel.org>; Mon, 20 Jun 2022 02:53:17 -0700 (PDT)
Received: by mail-il1-f200.google.com with SMTP id p12-20020a056e02144c00b002d196a4d73eso7174906ilo.18
        for <stable@vger.kernel.org>; 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=b9krf0f5culChbuGEIQxG8hmCbqqzv9bRzIog6tsDiv6SGwAEdpTsxt+zHDds/+Lrw
         LN8ybhWdCZNX52htjWey42UTHWIt1KTB+eGqRTtBkwdq4FHYM3teE5xwRQ9JP1n9WHhU
         s6g71dgZoIQZuw/fklr6h306WoARjK6X8EYKtc/UekiNDM03gWlrOMvbJ+TJTmNN3vRt
         Kjs/PypEL0QOKuLxJPEUKILEKeYM5uxeKcHBuCzITmKA9iv4psOvJfFV8cLUdqXNGM+Q
         +JHSDofFKRNDDnI3XQQVHXG/U4JEuC0A7+e2xR72GYQtR3nXSB0+UWNpPokzFSUq5KIH
         dFsA==
X-Gm-Message-State: AJIora9KANg97blMfUzxE4DPF5DRNdwDgRZLhgIKRsUID/VpFGd0lHM2
        AFpZ82aIe6h6oVFsgqxXvRP/YtZCOsqt+4QqlFiuW5gDI/kF
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 <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.