From: Peter Zijlstra <peterz@infradead.org>
To: Yang Shi <yang.shi@linaro.org>
Cc: tj@kernel.org, mingo@redhat.com, lizefan@huawei.com,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linaro-kernel@lists.linaro.org
Subject: Re: [linux-next PATCH] sched: cgroup: enable interrupt before calling threadgroup_change_begin
Date: Sat, 23 Apr 2016 11:14:47 +0200 [thread overview]
Message-ID: <20160423091447.GA3430@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1461383788-15102-1-git-send-email-yang.shi@linaro.org>
On Fri, Apr 22, 2016 at 08:56:28PM -0700, Yang Shi wrote:
> When kernel oops happens in some kernel thread, i.e. kcompactd in the test,
> the below bug might be triggered by the oops handler:
What are you trying to fix? You already oopsed the thing is wrecked.
next prev parent reply other threads:[~2016-04-23 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 3:56 [linux-next PATCH] sched: cgroup: enable interrupt before calling threadgroup_change_begin Yang Shi
2016-04-23 9:14 ` Peter Zijlstra [this message]
2016-04-25 17:35 ` Shi, Yang
2016-04-25 21:43 ` Shi, Yang
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=20160423091447.GA3430@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=tj@kernel.org \
--cc=yang.shi@linaro.org \
/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