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 647D6C43334
	for <stable@archiver.kernel.org>; Mon,  4 Jul 2022 09:54:19 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S233946AbiGDJyS (ORCPT <rfc822;stable@archiver.kernel.org>);
        Mon, 4 Jul 2022 05:54:18 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47300 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S229961AbiGDJyR (ORCPT
        <rfc822;stable@vger.kernel.org>); Mon, 4 Jul 2022 05:54:17 -0400
Received: from mail-io1-f71.google.com (mail-io1-f71.google.com [209.85.166.71])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B8F95DEA8
        for <stable@vger.kernel.org>; Mon,  4 Jul 2022 02:54:14 -0700 (PDT)
Received: by mail-io1-f71.google.com with SMTP id p16-20020a5d8b90000000b006750eb6b95dso5466730iol.11
        for <stable@vger.kernel.org>; Mon, 04 Jul 2022 02:54:14 -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=bPI3m/FjhiR38y09y3FaxnPOmEUM0Qq+Xh1mMgajiLU6XYWLBEyexBzjMzgFe2zTBK
         eJ0jQuKbzaXEGiOHMqfiBn1s3ywOqn1GQDU8BwJFJsZnmL0Yc1Bi9pUuVbmgqp0zqNhT
         p3y8hksFcVrNDWStJlSl49mvsrEElCkuQvPflMLElcoRSXMEP+qz/9E7hlqpLWtKF4G0
         YJUPdnNilQR3WUEIoPg+AGjnc9TsDgohmD7Nu9aUM7G+CB9GzSm4X0n3NZjiKGb/uiBl
         pVW1YzzB3HlbW/apogT0ydvVDqUWMFKQwTM0XbEpkYGAdZuVOcRaZO4mVZS2Gwb9LAXV
         VyAg==
X-Gm-Message-State: AJIora/QHcX/YnF14yuBtDUBvMQfpqblh9Yb2TzotqUTBgJWXVhyUula
        A0rAVPy/rmIBqz1HtQ7M2XLxFli4T8N8fwlSSbnnzFbMsQNn
X-Google-Smtp-Source: AGRyM1uVAx2t8fSOR2KLN2tAOPiUaRp3izLzYWRdEEBPt99xhRwEmPj9yiT6KWURtcER3vu/Lsr21nC1ku8Hk8QVAofPc1lwnppx
MIME-Version: 1.0
X-Received: by 2002:a05:6602:3689:b0:675:49c2:504e with SMTP id
 bf9-20020a056602368900b0067549c2504emr15029553iob.201.1656928454096; Mon, 04
 Jul 2022 02:54:14 -0700 (PDT)
Date:   Mon, 04 Jul 2022 02:54:14 -0700
In-Reply-To: <000000000000b960c00594598949@google.com>
X-Google-Appengine-App-Id: s~syzkaller
X-Google-Appengine-App-Id-Alias: syzkaller
Message-ID: <000000000000ecc7e905e2f7b764@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.