From: Rusty Russell <rusty@rustcorp.com.au>
To: lkp@lists.01.org
Subject: Re: [microcode/load_module] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7094 __might_sleep+0x51/0x16f()
Date: Thu, 07 Aug 2014 21:26:15 +0930 [thread overview]
Message-ID: <87r40scy3k.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20140807104140.GN19379@twins.programming.kicks-ass.net>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
Peter Zijlstra <peterz@infradead.org> writes:
> On Wed, Aug 06, 2014 at 05:12:24AM +0800, Fengguang Wu wrote:
>> Greetings,
>>
>> Here is a microcode/load_module error triggered by debug check commit
>> 64c2181bc433b17f04da8fe8592aa83cceac9606 ("sched: Debug nested
>> sleeps"):
Hmm, google lead me to that. Yuck, that's subtle.
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Reported-by: Fengguang Wu <fengguang.wu@intel.com>
> Signed-off-by: Peter Zijlstra <peterz@infradead.org>
> Link: http://lkml.kernel.org/n/tip-xtd4qlahotb7ar4bmo9lapz8(a)git.kernel.org
> ---
> kernel/module.c | 26 ++++++++++++++++++++++++--
> 1 file changed, 24 insertions(+), 2 deletions(-)
>
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -3094,6 +3094,28 @@ static int may_init_module(void)
> return 0;
> }
>
> +int wait_finished_loading(struct module *mod)
> +{
Is this something we can generalize? At least needs a comment on
why we don't just use the normal wait_event_interruptible...
Cheers,
Rusty.
WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Peter Zijlstra <peterz@infradead.org>,
Fengguang Wu <fengguang.wu@intel.com>
Cc: x86@kernel.org, LKML <linux-kernel@vger.kernel.org>, lkp@01.org
Subject: Re: [microcode/load_module] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7094 __might_sleep+0x51/0x16f()
Date: Thu, 07 Aug 2014 21:26:15 +0930 [thread overview]
Message-ID: <87r40scy3k.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20140807104140.GN19379@twins.programming.kicks-ass.net>
Peter Zijlstra <peterz@infradead.org> writes:
> On Wed, Aug 06, 2014 at 05:12:24AM +0800, Fengguang Wu wrote:
>> Greetings,
>>
>> Here is a microcode/load_module error triggered by debug check commit
>> 64c2181bc433b17f04da8fe8592aa83cceac9606 ("sched: Debug nested
>> sleeps"):
Hmm, google lead me to that. Yuck, that's subtle.
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Reported-by: Fengguang Wu <fengguang.wu@intel.com>
> Signed-off-by: Peter Zijlstra <peterz@infradead.org>
> Link: http://lkml.kernel.org/n/tip-xtd4qlahotb7ar4bmo9lapz8@git.kernel.org
> ---
> kernel/module.c | 26 ++++++++++++++++++++++++--
> 1 file changed, 24 insertions(+), 2 deletions(-)
>
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -3094,6 +3094,28 @@ static int may_init_module(void)
> return 0;
> }
>
> +int wait_finished_loading(struct module *mod)
> +{
Is this something we can generalize? At least needs a comment on
why we don't just use the normal wait_event_interruptible...
Cheers,
Rusty.
next prev parent reply other threads:[~2014-08-07 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 21:12 [microcode/load_module] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7094 __might_sleep+0x51/0x16f() Fengguang Wu
2014-08-05 21:12 ` Fengguang Wu
2014-08-07 10:41 ` Peter Zijlstra
2014-08-07 10:41 ` Peter Zijlstra
2014-08-07 11:56 ` Rusty Russell [this message]
2014-08-07 11:56 ` Rusty Russell
2014-08-07 12:11 ` Peter Zijlstra
2014-08-07 12:11 ` Peter Zijlstra
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=87r40scy3k.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=lkp@lists.01.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 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.