Re: [setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-07 Thread Peter Zijlstra
On Thu, Aug 07, 2014 at 07:25:14PM +0200, Peter Zijlstra wrote: > > This isn't the only place that we queue a message for the signalling > > daemon after a prepare_to_wait() uninterruptibly so this patch would > > be incomplete as is. > > I'm not sure I follow, this is the only place you do so

Re: [setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-07 Thread Peter Zijlstra
On Thu, Aug 07, 2014 at 12:59:48PM -0400, chas williams - CONTRACTOR wrote: > On Thu, 7 Aug 2014 17:17:41 +0200 > Peter Zijlstra wrote: > > > Subject: atm: Fix blocking in wait loop > > > > One should not call blocking primitives inside a wait loop, since both > > require task_struct::state to

Re: [setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-07 Thread chas williams - CONTRACTOR
On Thu, 7 Aug 2014 17:17:41 +0200 Peter Zijlstra wrote: > Subject: atm: Fix blocking in wait loop > > One should not call blocking primitives inside a wait loop, since both > require task_struct::state to sleep, so the inner will destroy the outer > state. > > In this instance sigd_enq() will

Re: [setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-07 Thread Peter Zijlstra
On Wed, Aug 06, 2014 at 05:46:24AM +0800, Fengguang Wu wrote: > Greetings, > > Here is a microcode/load_module error triggered by debug check commit > 64c2181bc433b17f04da8fe8592aa83cceac9606 ("sched: Debug nested sleeps"): > > [main] Setsockopt(1 8 80d1000 4) on fd 21 [1:2:1] > [main]

Re: [setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-07 Thread Peter Zijlstra
On Wed, Aug 06, 2014 at 05:46:24AM +0800, Fengguang Wu wrote: Greetings, Here is a microcode/load_module error triggered by debug check commit 64c2181bc433b17f04da8fe8592aa83cceac9606 (sched: Debug nested sleeps): [main] Setsockopt(1 8 80d1000 4) on fd 21 [1:2:1] [main] Setsockopt(1 2f

Re: [setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-07 Thread chas williams - CONTRACTOR
On Thu, 7 Aug 2014 17:17:41 +0200 Peter Zijlstra pet...@infradead.org wrote: Subject: atm: Fix blocking in wait loop One should not call blocking primitives inside a wait loop, since both require task_struct::state to sleep, so the inner will destroy the outer state. In this instance

Re: [setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-07 Thread Peter Zijlstra
On Thu, Aug 07, 2014 at 12:59:48PM -0400, chas williams - CONTRACTOR wrote: On Thu, 7 Aug 2014 17:17:41 +0200 Peter Zijlstra pet...@infradead.org wrote: Subject: atm: Fix blocking in wait loop One should not call blocking primitives inside a wait loop, since both require

Re: [setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-07 Thread Peter Zijlstra
On Thu, Aug 07, 2014 at 07:25:14PM +0200, Peter Zijlstra wrote: This isn't the only place that we queue a message for the signalling daemon after a prepare_to_wait() uninterruptibly so this patch would be incomplete as is. I'm not sure I follow, this is the only place you do so while then

Re: [setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-05 Thread Fengguang Wu
On Wed, Aug 06, 2014 at 05:46:24AM +0800, Fengguang Wu wrote: > Greetings, > > Here is a microcode/load_module error triggered by debug check commit Sorry for the copy error! This warning is not related to microcode/load_module.. Thanks, Fengguang -- To unsubscribe from this list: send the line

[setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-05 Thread Fengguang Wu
Greetings, Here is a microcode/load_module error triggered by debug check commit 64c2181bc433b17f04da8fe8592aa83cceac9606 ("sched: Debug nested sleeps"): [main] Setsockopt(1 8 80d1000 4) on fd 21 [1:2:1] [main] Setsockopt(1 2f 80d1000 4) on fd 22 [4:2:60] [ 14.027148] [ cut here

[setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-05 Thread Fengguang Wu
Greetings, Here is a microcode/load_module error triggered by debug check commit 64c2181bc433b17f04da8fe8592aa83cceac9606 (sched: Debug nested sleeps): [main] Setsockopt(1 8 80d1000 4) on fd 21 [1:2:1] [main] Setsockopt(1 2f 80d1000 4) on fd 22 [4:2:60] [ 14.027148] [ cut here

Re: [setsockopt] WARNING: CPU: 0 PID: 1444 at kernel/sched/core.c:7088 __might_sleep+0x51/0x16f()

2014-08-05 Thread Fengguang Wu
On Wed, Aug 06, 2014 at 05:46:24AM +0800, Fengguang Wu wrote: Greetings, Here is a microcode/load_module error triggered by debug check commit Sorry for the copypaste error! This warning is not related to microcode/load_module.. Thanks, Fengguang -- To unsubscribe from this list: send the