From: syzbot <syzbot+006987d1be3586e13555@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [arm-msm?] [net?] memory leak in radix_tree_insert (2)
Date: Fri, 08 Dec 2023 00:17:05 -0800 [thread overview]
Message-ID: <000000000000b5b714060bfb35fd@google.com> (raw)
In-Reply-To: <20231208074438.4102005-1-lizhi.xu@windriver.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
lib/radix-tree.c:591:17: error: implicit declaration of function 'node_tag_set'; did you mean 'root_tag_set'? [-Werror=implicit-function-declaration]
lib/radix-tree.c:594:25: error: implicit declaration of function 'node_tag_clear'; did you mean 'root_tag_clear'? [-Werror=implicit-function-declaration]
lib/radix-tree.c:596:9: error: implicit declaration of function 'replace_slot'; did you mean 'replace_fops'? [-Werror=implicit-function-declaration]
lib/radix-tree.c:843:13: error: static declaration of 'replace_slot' follows non-static declaration
lib/radix-tree.c:958:13: error: static declaration of 'node_tag_set' follows non-static declaration
lib/radix-tree.c:1015:13: error: static declaration of 'node_tag_clear' follows non-static declaration
Tested on:
commit: 33cc938e Linux 6.7-rc4
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=37d1b8bb20150e6
dashboard link: https://syzkaller.appspot.com/bug?extid=006987d1be3586e13555
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=178c2ed4e80000
next parent reply other threads:[~2023-12-08 8:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231208074438.4102005-1-lizhi.xu@windriver.com>
2023-12-08 8:17 ` syzbot [this message]
[not found] <20231211051540.1882463-1-lizhi.xu@windriver.com>
2023-12-11 5:52 ` [syzbot] [arm-msm?] [net?] memory leak in radix_tree_insert (2) syzbot
[not found] <20231211042442.1442601-1-lizhi.xu@windriver.com>
2023-12-11 4:41 ` syzbot
[not found] <tencent_5DCBB36DE37A697AA3A5A44C176557784605@qq.com>
2023-12-10 8:13 ` syzbot
[not found] <tencent_F5872516BA75BB5A33CC9E661B2F4BB81B08@qq.com>
2023-12-10 6:30 ` syzbot
[not found] <tencent_9CCF8C7BE26EA02CF16DE894A8E88EEDA60A@qq.com>
2023-12-10 5:39 ` syzbot
[not found] <tencent_FDEC79DE6C3C2C356F409770E8F6EFC2CE0A@qq.com>
2023-12-10 4:48 ` syzbot
[not found] <tencent_1571C9B12ED06EED4CAC67FD86C052FC4606@qq.com>
2023-12-10 4:08 ` syzbot
[not found] <tencent_0E30CFAC0DE825820DBC923D5DE75DAF1907@qq.com>
2023-12-10 1:19 ` syzbot
[not found] <tencent_140DE9120A5D895DEA192FCF900D9FA5F807@qq.com>
2023-12-09 7:10 ` syzbot
[not found] <tencent_366443176A9766C6D8D36A8374896363B605@qq.com>
2023-12-09 7:05 ` syzbot
[not found] <tencent_170675C9766F66183C77360A96A237AE4B09@qq.com>
2023-12-09 5:17 ` syzbot
[not found] <20231208094538.2466543-1-lizhi.xu@windriver.com>
2023-12-08 10:59 ` syzbot
[not found] <20231208065944.3611430-1-lizhi.xu@windriver.com>
2023-12-08 7:16 ` syzbot
[not found] <20231208055640.1895881-1-lizhi.xu@windriver.com>
2023-12-08 6:15 ` syzbot
[not found] <20231208041309.2699993-1-lizhi.xu@windriver.com>
2023-12-08 5:17 ` syzbot
2023-12-08 0:52 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=000000000000b5b714060bfb35fd@google.com \
--to=syzbot+006987d1be3586e13555@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--cc=syzkaller-bugs@googlegroups.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.