From: syzbot ci <syzbot+cif33cbad46bbf0ec2@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: sched: Add support for long task name
Date: Thu, 10 Sep 2026 11:50:17 -0700 [thread overview]
Message-ID: <6aa2fbe9.f2639fcc.29487d.001a.GAE@google.com> (raw)
syzbot ci has tested the following series
[v6] sched: Add support for long task name
https://lore.kernel.org/all/20260910-tonyk-long_name-v6-0-d70afbf194c5@igalia.com
* [PATCH v6 1/6] treewide: Get rid of get_task_comm()
* [PATCH v6 2/6] treewide: Replace memcpy(..., current->comm) with copy_task_comm()
* [PATCH v6 3/6] lib/string_kunit: Add test for copy_task_comm()
* [PATCH v6 4/6] sched: Extend task command name with TASK_COMM_EXT_LEN
* [PATCH v6 5/6] prctl: Add support for long user thread names
* [PATCH v6 6/6] selftests: prctl: Add test for long thread names
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/82558e77-0c89-4bfd-b82d-53143ea6a0d6
***
kernel build error
tree: axboe
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/axboe/linux.git
base: 50d05c7c76c96b90462f24debacca971d2e86713
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/4b791023-c565-44b8-8a9b-dc4d3a1b1950/config
security/smack/smack_lsm.c:141:2: error: incompatible pointer types initializing 'const char *' with an expression of type 'struct task_struct *' [-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.
To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[akpm@linux-foundation.org andrealmeid@igalia.com andrii.nakryiko@gmail.com arnaldo.melo@gmail.com brauner@kernel.org david.laight.linux@gmail.com juri.lelli@redhat.com kees@kernel.org kernel-dev@igalia.com laoar.shao@gmail.com linux-api@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org linux-trace-kernel@vger.kernel.org mathieu.desnoyers@efficios.com peterz@infradead.org pmladek@suse.com rostedt@goodmis.org shuah@kernel.org torvalds@linux-foundation.org vincent.guittot@linaro.org willy@infradead.org]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
next reply other threads:[~2026-09-10 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 18:50 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-17 19:49 [moderation/CI] Re: sched: Add support for long task name syzbot ci
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=6aa2fbe9.f2639fcc.29487d.001a.GAE@google.com \
--to=syzbot+cif33cbad46bbf0ec2@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