public inbox for syzbot@lists.linux.dev
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci0db69c802d6f7a0e@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Implementation of Dynamic Housekeeping & Enhanced Isolation (DHEI)
Date: Wed, 25 Mar 2026 03:25:07 -0700	[thread overview]
Message-ID: <69c3b803.050a0220.abc16.0014.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] Implementation of Dynamic Housekeeping & Enhanced Isolation (DHEI)
https://lore.kernel.org/all/20260325-dhei-v12-final-v1-0-919cca23cadf@gmail.com
* [PATCH 01/15] sched/isolation: Support dynamic allocation for housekeeping masks
* [PATCH 02/15] sched/isolation: Introduce housekeeping notifier infrastructure
* [PATCH 03/15] sched/isolation: Separate housekeeping types in enum hk_type
* [PATCH 04/15] genirq: Support dynamic migration for managed interrupts
* [PATCH 05/15] rcu: Support runtime NOCB initialization and dynamic offloading
* [PATCH 06/15] sched/core: Dynamically update scheduler domain housekeeping mask
* [PATCH 07/15] watchdog: Allow runtime toggle of lockup detector affinity
* [PATCH 08/15] workqueue: Support dynamic housekeeping mask updates
* [PATCH 09/15] mm/compaction: Support dynamic housekeeping mask updates for kcompactd
* [PATCH 10/15] tick/nohz: Transition to dynamic full dynticks state management
* [PATCH 11/15] sched/isolation: Implement SMT-aware isolation and safety guards
* [PATCH 12/15] sched/isolation: Bridge boot-time parameters with dynamic isolation
* [PATCH 13/15] sched/isolation: Implement sysfs interface for dynamic housekeeping
* [PATCH 14/15] Documentation: isolation: Document DHEI sysfs interfaces
* [PATCH 15/15] selftests: dhei: Add functional tests for dynamic housekeeping

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/bb8ddd2b-bd3f-479b-b34e-c924fd9f53e8

***

kernel build error

tree:      bpf-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base:      63804fed149a6750ffd28610c5c1c98cce6bd377
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/968f9f5e-f0b1-4c6c-b75e-2dab0088f9e5/config

kernel/rcu/tree_nocb.h:1706:13: error: redefinition of 'rcu_spawn_cpu_nocb_kthread'

***

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 anna-maria@linutronix.de boqun.feng@gmail.com bsegall@google.com dietmar.eggemann@arm.com frederic@kernel.org hannes@cmpxchg.org jackmanb@google.com jiangshanlai@gmail.com joelagnelf@nvidia.com josh@joshtriplett.org juri.lelli@redhat.com linux-kernel@vger.kernel.org linux-kselftest@vger.kernel.org linux-mm@kvack.org mathieu.desnoyers@efficios.com mgorman@suse.de mhocko@suse.com mingo@kernel.org mingo@redhat.com neeraj.upadhyay@kernel.org paulmck@kernel.org peterz@infradead.org qiang.zhang@linux.dev rcu@vger.kernel.org realwujing@gmail.com rostedt@goodmis.org shuah@kernel.org surenb@google.com tglx@kernel.org tj@kernel.org urezki@gmail.com vbabka@suse.cz vincent.guittot@linaro.org vschneid@redhat.com ziy@nvidia.com]

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-03-25 10:25 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=69c3b803.050a0220.abc16.0014.GAE@google.com \
    --to=syzbot+ci0db69c802d6f7a0e@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