From: syzbot ci <syzbot+ci74d3533275516618@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Memory Controller eBPF support
Date: Tue, 18 Nov 2025 18:24:48 -0800 [thread overview]
Message-ID: <691d2a70.a70a0220.d98e3.0002.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] Memory Controller eBPF support
https://lore.kernel.org/all/cover.1763457705.git.zhuhui@kylinos.cn
* [RFC PATCH 1/3] memcg: add eBPF struct ops support for memory charging
* [RFC PATCH 2/3] selftests/bpf: add memcg eBPF struct ops test
* [RFC PATCH 3/3] samples/bpf: add example memcg eBPF program
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/4870ca10-e779-4263-bbf0-620b6b3f7339
***
kernel build error
tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: 4722981cca373a338bbcf3a93ecf7144a892b03b
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/6158e239-7d3d-4449-a22c-d0143decb63f/config
mm/memcontrol.c:2341:14: error: assigning to 'unsigned long' from incompatible type 'void'
***
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 andrii@kernel.org ast@kernel.org bpf@vger.kernel.org brauner@kernel.org brgerst@gmail.com cgroups@vger.kernel.org daniel@iogearbox.net eddyz87@gmail.com geliang@kernel.org hannes@cmpxchg.org haoluo@google.com hui.zhu@linux.dev jeffxu@chromium.org john.fastabend@gmail.com jolsa@kernel.org kees@kernel.org kernel@jfarr.cc kpsingh@kernel.org linux-kernel@vger.kernel.org linux-kselftest@vger.kernel.org linux-mm@kvack.org martin.lau@linux.dev masahiroy@kernel.org mhocko@kernel.org mkoutny@suse.com muchun.song@linux.dev nathan@kernel.org ojeda@kernel.org peterz@infradead.org rdunlap@infradead.org roman.gushchin@linux.dev sdf@fomichev.me shakeel.butt@linux.dev shuah@kernel.org song@kernel.org tj@kernel.org yonghong.song@linux.dev zhuhui@kylinos.cn]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-11-19 2:24 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=691d2a70.a70a0220.d98e3.0002.GAE@google.com \
--to=syzbot+ci74d3533275516618@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox