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
Subject: Re: KASAN: use-after-free Read in tc_chain_fill_node
Date: Mon, 15 Aug 2022 02:57:13 -0700 [thread overview]
Message-ID: <000000000000fbab2f05e644a744@google.com> (raw)
In-Reply-To: <000000000000b960c00594598949@google.com>
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.
next prev parent reply other threads:[~2022-08-15 9:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000b960c00594598949@google.com>
2022-03-14 9:47 ` KASAN: use-after-free Read in tc_chain_fill_node syzbot
2022-03-28 9:48 ` syzbot
2022-04-11 9:49 ` syzbot
2022-04-25 9:50 ` syzbot
2022-05-09 9:51 ` syzbot
2022-05-23 9:52 ` syzbot
2022-06-06 9:52 ` syzbot
2022-06-20 9:53 ` syzbot
2022-07-04 9:54 ` syzbot
2022-07-18 9:55 ` syzbot
2022-08-01 9:56 ` syzbot
2022-08-15 9:57 ` syzbot [this message]
2022-08-29 9:57 ` syzbot
2022-09-12 9:58 ` syzbot
2022-09-26 9:58 ` syzbot
2022-10-10 9:59 ` syzbot
2022-10-24 10:00 ` syzbot
2022-11-07 10:01 ` syzbot
2022-11-21 10:02 ` syzbot
2022-12-05 10:03 ` syzbot
2022-12-19 10:04 ` syzbot
2023-01-02 10:05 ` syzbot
2023-01-16 10:05 ` syzbot
2023-01-30 10:06 ` syzbot
2023-02-13 10:07 ` syzbot
2023-02-27 10:08 ` syzbot
2023-03-13 10:08 ` syzbot
2023-03-27 10:09 ` syzbot
2023-04-10 10:10 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000fbab2f05e644a744@google.com \
--to=syzbot+5f229e48cccc804062c0@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@mellanox.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzkaller-lts-bugs@googlegroups.com \
--cc=vladbu@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.