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 C378BC47090 for ; Mon, 5 Dec 2022 10:03:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231334AbiLEKDk (ORCPT ); Mon, 5 Dec 2022 05:03:40 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45372 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230012AbiLEKDj (ORCPT ); Mon, 5 Dec 2022 05:03:39 -0500 Received: from mail-il1-f199.google.com (mail-il1-f199.google.com [209.85.166.199]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CCC43CF6 for ; Mon, 5 Dec 2022 02:03:38 -0800 (PST) Received: by mail-il1-f199.google.com with SMTP id i11-20020a056e02152b00b00303642498daso1465732ilu.5 for ; Mon, 05 Dec 2022 02:03:38 -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=sVvRetvU66viZg03zt42J481swUWQOVgkFgrLPfYY/8=; b=B370jMWeMmvW1FbB9DpLwbodUBRZ24q75TlDY4DYg0gjV7d3VwRiMcvAIzXbqMLF9T JjYlAkOJ3YgDF6hWCbXq4w2H2XFASPfXZjXdjy5dQjC64+vx/rZwOWoov+yz9ImRqSvE zo4KN/tEcvddTaUJCn/v7d0/IW8oRYSqMEpeE9I1GjfKaSJmIgk63mrr2gIX+desSLLa 8GJNbzzM8TfXOnkMs+PqDdsqoyvLbAUHgsjDSOuukBU3ettfvWSJKJnw3Ge08w1LYk8g M0qKysRS/2gg/TUjV9Fewu0sAZDQFhbbmjx8UEpxlhgzrXx2ztQ1Z+1/lvc0x1/SPk7K EudQ== X-Gm-Message-State: ANoB5pl7C8wfpi+gkcWjEeGiJkFrmmZTKwILswGi8TcWi7xTsYM0OJ1c 4JmzDTh54KH9IWxKvLNwml1rxbo9sZWaU7gzRlSaBnt3JwQQ X-Google-Smtp-Source: AA0mqf6A9nhl03BO/uU380Ihl2+zu7W4+sPhFjI9s4qoei5e3boHFr9wue4FtJCqu+xvEjayVYISuxBkecYYw099cK+iDcEU+dyN MIME-Version: 1.0 X-Received: by 2002:a02:ac92:0:b0:38a:219a:d627 with SMTP id x18-20020a02ac92000000b0038a219ad627mr5844842jan.174.1670234618187; Mon, 05 Dec 2022 02:03:38 -0800 (PST) Date: Mon, 05 Dec 2022 02:03:38 -0800 In-Reply-To: <000000000000b960c00594598949@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000001bd6ea05ef11cd1c@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: 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.