From: syzbot <syzbot+42cfec52b6508887bbe8@syzkaller.appspotmail.com>
To: alexander.mikhalitsyn@virtuozzo.com, davem@davemloft.net,
den@openvz.org, dsahern@kernel.org, edumazet@google.com,
f.fainelli@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
nogikh@google.com, pabeni@redhat.com, razor@blackwall.org,
syzkaller-bugs@googlegroups.com,
thomas.zeitlhofer+lkml@ze-it.at, thomas.zeitlhofer@ze-it.at,
wangyuweihx@gmail.com
Subject: Re: [syzbot] memory leak in ___neigh_create (2)
Date: Thu, 04 Apr 2024 11:26:18 -0700 [thread overview]
Message-ID: <000000000000ad5b3b06154979cd@google.com> (raw)
In-Reply-To: <000000000000a62351060e363bdc@google.com>
This bug is marked as fixed by commit:
net: stop syzbot
But I can't find it in the tested trees[1] 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.
Kernel: Linux
Dashboard link: https://syzkaller.appspot.com/bug?extid=42cfec52b6508887bbe8
---
[1] I expect the commit to be present in:
1. for-kernelci branch of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
2. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
3. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
4. main branch of
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
The full list of 9 trees can be found at
https://syzkaller.appspot.com/upstream/repos
next prev parent reply other threads:[~2024-04-04 18:26 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 17:32 [syzbot] [net?] memory leak in ___neigh_create (2) syzbot
2024-01-05 17:33 ` syzbot
2024-01-05 17:34 ` syzbot
2024-01-05 17:35 ` syzbot
2024-01-05 17:36 ` syzbot
2024-01-05 17:37 ` syzbot
2024-01-05 17:38 ` syzbot
2024-01-05 17:39 ` syzbot
2024-01-05 17:40 ` syzbot
2024-01-05 17:41 ` syzbot
2024-01-05 17:42 ` syzbot
2024-01-05 17:43 ` syzbot
2024-01-05 17:44 ` syzbot
2024-01-05 17:45 ` syzbot
2024-01-05 17:46 ` syzbot
2024-01-05 17:47 ` syzbot
2024-01-05 17:48 ` syzbot
2024-01-05 17:49 ` syzbot
2024-01-05 17:50 ` syzbot
2024-01-05 17:51 ` syzbot
2024-01-05 17:52 ` syzbot
2024-01-05 17:53 ` syzbot
2024-01-05 17:54 ` syzbot
2024-01-05 17:55 ` syzbot
2024-01-05 17:56 ` syzbot
2024-01-05 17:57 ` syzbot
2024-01-05 17:58 ` syzbot
2024-01-05 17:59 ` syzbot
2024-01-05 18:00 ` syzbot
2024-01-05 18:01 ` syzbot
2024-01-05 18:02 ` syzbot
2024-01-05 18:03 ` syzbot
2024-01-05 18:04 ` syzbot
2024-01-05 18:05 ` syzbot
2024-01-05 18:06 ` syzbot
2024-01-05 18:07 ` syzbot
2024-01-05 18:08 ` syzbot
2024-01-05 18:09 ` syzbot
2024-01-05 18:10 ` syzbot
2024-01-05 18:11 ` syzbot
2024-01-05 18:12 ` syzbot
2024-01-05 18:13 ` syzbot
2024-01-05 18:14 ` syzbot
2024-01-05 18:15 ` syzbot
2024-01-05 18:16 ` syzbot
2024-01-05 18:17 ` syzbot
2024-01-05 18:18 ` syzbot
2024-01-05 18:19 ` syzbot
2024-01-05 18:20 ` Florian Fainelli
2024-01-05 18:20 ` syzbot
2024-01-05 18:21 ` syzbot
2024-01-05 18:22 ` syzbot
2024-01-05 18:23 ` syzbot
2024-01-05 18:25 ` Eric Dumazet
2024-01-05 18:24 ` syzbot
2024-01-05 18:25 ` syzbot
2024-01-05 18:26 ` syzbot
2024-01-05 18:27 ` syzbot
2024-01-05 18:28 ` syzbot
2024-01-05 18:29 ` syzbot
2024-01-05 18:30 ` syzbot
2024-01-05 18:31 ` syzbot
2024-01-05 18:32 ` syzbot
2024-01-05 18:33 ` syzbot
2024-01-05 18:34 ` syzbot
2024-01-05 18:35 ` syzbot
2024-01-05 18:36 ` syzbot
2024-01-05 18:37 ` syzbot
2024-01-05 18:38 ` syzbot
2024-01-05 18:39 ` syzbot
2024-01-05 18:40 ` syzbot
2024-01-05 18:41 ` syzbot
2024-01-05 18:46 ` Aleksandr Nogikh
2024-04-04 18:26 ` syzbot [this message]
2024-04-18 18:27 ` [syzbot] " syzbot
2024-05-02 18:28 ` syzbot
2024-05-16 18:28 ` syzbot
2024-05-30 18:29 ` syzbot
2024-06-13 18:30 ` syzbot
2024-06-27 18:31 ` syzbot
2024-07-11 18:32 ` syzbot
2024-07-25 18:33 ` syzbot
2024-08-08 18:34 ` syzbot
2024-08-22 18:35 ` syzbot
2024-09-05 11:54 ` [syzbot] 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=000000000000ad5b3b06154979cd@google.com \
--to=syzbot+42cfec52b6508887bbe8@syzkaller.appspotmail.com \
--cc=alexander.mikhalitsyn@virtuozzo.com \
--cc=davem@davemloft.net \
--cc=den@openvz.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nogikh@google.com \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=thomas.zeitlhofer+lkml@ze-it.at \
--cc=thomas.zeitlhofer@ze-it.at \
--cc=wangyuweihx@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).