From: syzbot ci <syzbot+ci976947bc4b8c0f5f@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: Sun, 17 May 2026 12:49:08 -0700 [thread overview]
Message-ID: <6a0a1bb4.a00a0220.300e5b.000b.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] sched: Add support for long task name
https://lore.kernel.org/all/20260517-tonyk-long_name-v1-0-3c282eaa91e2@igalia.com
* [PATCH 1/6] sched: Update get_task_comm() comment
* [PATCH 2/6] treewide: Get rid of get_task_comm()
* [PATCH 3/6] string: Introduce strtostr() for safe and performance string copies
* [PATCH 4/6] sched: Extend task command name to 64 bytes
* [PATCH 5/6] prctl: Add support for long user thread names
* [PATCH 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/ebe3a5a0-c138-4f99-ad22-8a880dc176ca
***
kernel build error
tree: bpf
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf.git
base: 5d6919055dec134de3c40167a490f33c74c12581
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/108b7ff7-5ce1-4980-a6f7-e69a669ec7e6/config
net/netfilter/nf_tables_api.c:9714:46: error: incompatible integer to pointer conversion passing 'ssize_t' (aka 'long') to parameter of type 'const char *' [-Wint-conversion]
***
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 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:
[akpm@linux-foundation.org andrealmeid@igalia.com andrii.nakryiko@gmail.com arnaldo.melo@gmail.com bhupesh@igalia.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 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
reply other threads:[~2026-05-17 19:49 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=6a0a1bb4.a00a0220.300e5b.000b.GAE@google.com \
--to=syzbot+ci976947bc4b8c0f5f@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