From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kernel test robot <oliver.sang@intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, x86@kernel.org,
Chen Yu <yu.c.chen@intel.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Shrikanth Hegde <sshegde@linux.ibm.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Srikar Dronamraju <srikar@linux.ibm.com>,
Mohini Narkhede <mohini.narkhede@intel.com>,
aubrey.li@linux.intel.com
Subject: Re: [tip:tmp.tmp] [sched/fair] eb2db043ab: BUG:kernel_NULL_pointer_dereference,address
Date: Thu, 27 Nov 2025 10:07:28 +0100 [thread overview]
Message-ID: <aSgU0IDhF4uam0JA@gmail.com> (raw)
In-Reply-To: <20251127083815.GZ3245006@noisy.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Thu, Nov 27, 2025 at 04:35:37PM +0800, kernel test robot wrote:
> >
> >
> > Hello,
> >
> > kernel test robot noticed "BUG:kernel_NULL_pointer_dereference,address" on:
> >
> > commit: eb2db043ab3a28ae76800f2a57e144420800d56d ("sched/fair: Skip sched_balance_running cmpxchg when balance is not due")
> > https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git tmp.tmp
>
> Not sure what this branch is, but tip/sched/core has the fixed commit.
Not sure how the test-bot picked up this temporary
branch and reported it despite it being gone from the
repo, but the branch hasn't been in -tip for days.
This report can be safely ignored.
Thanks,
Ingo
next prev parent reply other threads:[~2025-11-27 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 8:35 [tip:tmp.tmp] [sched/fair] eb2db043ab: BUG:kernel_NULL_pointer_dereference,address kernel test robot
2025-11-27 8:38 ` Peter Zijlstra
2025-11-27 9:07 ` Ingo Molnar [this message]
2025-11-28 1:42 ` Oliver Sang
2025-11-28 9:34 ` Peter Zijlstra
2025-12-02 5:11 ` Ingo Molnar
2025-12-03 6:54 ` Oliver Sang
2025-12-03 17:16 ` Ingo Molnar
2025-12-02 4:59 ` Ingo Molnar
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=aSgU0IDhF4uam0JA@gmail.com \
--to=mingo@kernel.org \
--cc=aubrey.li@linux.intel.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mohini.narkhede@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=srikar@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.