From: Peter Zijlstra <peterz@infradead.org>
To: Yuyang Du <yuyang.du@intel.com>
Cc: tglx@linutronix.de, mingo@redhat.com, fengguang.wu@intel.com,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org, Yuanhan Liu <yuanhan.liu@linux.intel.com>,
pjt@google.com, bsegall@google.com, rafael.j.wysocki@intel.com
Subject: Re: [LKP] [sched] kernel BUG at kernel/smpboot.c:134!
Date: Thu, 6 Nov 2014 11:45:13 +0100 [thread overview]
Message-ID: <20141106104513.GS10501@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20141105180758.GA19218@intel.com>
On Thu, Nov 06, 2014 at 02:07:58AM +0800, Yuyang Du wrote:
> Hi Peter and Thomas,
>
> LKP found a bug, and it was bisected to my rewrite patch:
> http://article.gmane.org/gmane.linux.kernel/1818393/
>
> But I really don't have a clue about why the patch can introduce
> such a bug, as the patch does not modify anything related. Or maybe
> the bug could be indirectly triggerd, just don't know how.
>
> To confirm it is not a false positive, we are rebasing the patch to
> 3.18-rc3 to try to reproduce it, it is now ongoing.
>
> In addition, I noticed this thread about the same symptom:
> http://thread.gmane.org/gmane.linux.kernel/1819348.
>
> Thomas should already have a fix to this. Right?
Not quite; see https://lkml.org/lkml/2014/6/26/554
Let me read that thread though, maybe I can make sense of it.
prev parent reply other threads:[~2014-11-06 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 4:29 [LKP] [sched] kernel BUG at kernel/smpboot.c:134! kernel test robot
2014-11-05 18:07 ` Yuyang Du
2014-11-06 10:45 ` Peter Zijlstra [this message]
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=20141106104513.GS10501@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@redhat.com \
--cc=pjt@google.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--cc=yuanhan.liu@linux.intel.com \
--cc=yuyang.du@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox