From: syzbot ci <syzbot+ciff443e73dc5d069c@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm/slab: mark alloc tags empty for sheafs allocated with __GFP_NO_OBJ_EXT
Date: Tue, 24 Feb 2026 14:01:34 -0800 [thread overview]
Message-ID: <699e1fbe.a00a0220.32abbc.0213.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] mm/slab: mark alloc tags empty for sheafs allocated with __GFP_NO_OBJ_EXT
https://lore.kernel.org/all/20260224165250.1322946-1-surenb@google.com
* [PATCH 1/1] mm/slab: mark alloc tags empty for sheafs allocated with __GFP_NO_OBJ_EXT
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/4dcc0e7e-2248-495a-8098-7296b41b37bd
***
kernel build error
tree: bpf
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf.git
base: 7dff99b354601dd01829e1511711846e04340a69
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/3c0ba432-938b-4b2e-9c1e-26f43fb0b029/config
mm/slub.c:2787:22: error: incompatible pointer types passing 'struct slab_sheaf *' to parameter of type 'struct slabobj_ext *' [-Werror,-Wincompatible-pointer-types]
***
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:
[00107082@163.com akpm@linux-foundation.org cl@gentwo.org harry.yoo@oracle.com linux-kernel@vger.kernel.org linux-mm@kvack.org rientjes@google.com roman.gushchin@linux.dev surenb@google.com vbabka@suse.cz]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-02-24 22:01 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=699e1fbe.a00a0220.32abbc.0213.GAE@google.com \
--to=syzbot+ciff443e73dc5d069c@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