From: syzbot ci <syzbot+ci7427a48d33cb9843@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: zram: Fix the issue that the write - back limits might overflow
Date: Tue, 18 Nov 2025 03:00:18 -0800 [thread overview]
Message-ID: <691c51c2.a70a0220.3124cb.00bf.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] zram: Fix the issue that the write - back limits might overflow
https://lore.kernel.org/all/tencent_2FEBA8888C5B7C3CC495E17C29EFE76BA805@qq.com
* [PATCH v2] zram: Fix the issue that the write - back limits might overflow
and found the following issue:
WARNING: kmalloc bug in bpf_prog_alloc_no_stats
Full report is available here:
https://ci.syzbot.org/series/259c5b30-7d81-45fe-a0e0-b283a12d6bfa
***
WARNING: kmalloc bug in bpf_prog_alloc_no_stats
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 41218ede767f6b218185af65ce919d0cade75f6b
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/e782f0b5-cca9-46b3-98b9-cd87f46fb439/config
------------[ cut here ]------------
Unexpected gfp: 0x400000 (__GFP_ACCOUNT). Fixing up to gfp: 0xdc0 (GFP_KERNEL|__GFP_ZERO). Fix your code!
WARNING: CPU: 1 PID: 6000 at mm/vmalloc.c:3938 vmalloc_fix_flags+0x9c/0xe0
Modules linked in:
CPU: 1 UID: 0 PID: 6000 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:vmalloc_fix_flags+0x9c/0xe0
Code: 81 e6 1f 52 ee ff 89 74 24 30 81 e3 e0 ad 11 00 89 5c 24 20 90 48 c7 c7 c0 b9 76 8b 4c 89 fa 89 d9 4d 89 f0 e8 75 2b 6e ff 90 <0f> 0b 90 90 8b 44 24 20 48 c7 04 24 0e 36 e0 45 4b c7 04 2c 00 00
RSP: 0018:ffffc90004fa7b00 EFLAGS: 00010246
RAX: 4ebf39c92d9eb400 RBX: 0000000000000dc0 RCX: ffff88816aa0d700
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: ffffc90004fa7b98 R08: ffff88823c624293 R09: 1ffff110478c4852
R10: dffffc0000000000 R11: ffffed10478c4853 R12: 1ffff920009f4f60
R13: dffffc0000000000 R14: ffffc90004fa7b20 R15: ffffc90004fa7b30
FS: 000055555cfc1500(0000) GS:ffff8882a9f36000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb90085c470 CR3: 0000000112060000 CR4: 00000000000006f0
Call Trace:
<TASK>
__vmalloc_noprof+0xf2/0x120
bpf_prog_alloc_no_stats+0x4a/0x4d0
bpf_prog_alloc+0x3c/0x1a0
bpf_prog_create_from_user+0xa7/0x440
do_seccomp+0x7b1/0xd90
__se_sys_prctl+0xc3c/0x1830
do_syscall_64+0xfa/0xfa0
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb900990b0d
Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 18 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 9d 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 1b 48 8b 54 24 18 64 48 2b 14 25 28 00 00 00
RSP: 002b:00007fff5f8ff980 EFLAGS: 00000246 ORIG_RAX: 000000000000009d
RAX: ffffffffffffffda RBX: 00007fb900a2cf80 RCX: 00007fb900990b0d
RDX: 00007fff5f8ff9e0 RSI: 0000000000000002 RDI: 0000000000000016
RBP: 00007fff5f8ff9f0 R08: 0000000000000006 R09: 0000000000000071
R10: 0000000000000071 R11: 0000000000000246 R12: 000000000000006d
R13: 00007fff5f8ffe18 R14: 00007fff5f900098 R15: 0000000000000000
</TASK>
***
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: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
The email will later be sent to:
[akpm@linux-foundation.org bgeffon@google.com licayy@outlook.com linux-block@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org minchan@kernel.org richardycc@google.com senozhatsky@chromium.org ywen.chen@foxmail.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-11-18 11:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=691c51c2.a70a0220.3124cb.00bf.GAE@google.com \
--to=syzbot+ci7427a48d33cb9843@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@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.