[moderation/CI] Re: mm: shrinker: Fix double-free in alloc_shrinker_info error path
syzbot ci <[email protected]> Sat, 11 Jul 2026 17:24:59 -0700
| Newsgroups | dev.linux.lists.syzbot |
|---|---|
| Message-ID | <[email protected]> |
syzbot ci has tested the following series [v1] mm: shrinker: Fix double-free in alloc_shrinker_info error path https://lore.kernel.org/all/[email protected] * [PATCH] mm: shrinker: Fix double-free in alloc_shrinker_info error path and found the following issue: kernel build error Full report is available here: https://ci.syzbot.org/series/348846f6-b8e9-4724-8320-654ad3472b53 *** kernel build error tree: mm-new URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git base: dc59e4fea9d83f03bad6bddf3fa2e52491777482 arch: amd64 compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6 config: https://ci.syzbot.org/builds/fb13ef19-37ba-420a-a80d-1be9633bdb35/config mm/shrinker.c:108:10: error: call to undeclared function 'shrinker_info_protected'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] mm/shrinker.c:108:8: error: incompatible integer to pointer conversion assigning to 'struct shrinker_info *' from 'int' [-Wint-conversion] mm/shrinker.c:117:30: error: conflicting types for 'shrinker_info_protected' *** If these findings have caused you to resend the series or submit a separate fix, please add the following tag to your commit message: Tested-by: [email protected] --- This report is generated by a bot. It may contain errors. syzbot ci engineers can be reached at [email protected]. To test a patch for this bug, please reply with `#syz test` (should be on a separate line). The patch should be attached to the email. Note: arguments like custom git repos and branches are not supported. The email will later be sent to: [[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]] If the report looks fine to you, reply with: #syz upstream If the report is a false positive, reply with #syz invalid