On Thu, 11 Sep 2014, Davidlohr Bueso wrote:
> On Thu, 2014-09-11 at 23:52 +0200, Thomas Gleixner wrote:
> > From: Thomas Gleixner
> > Date: Thu, 11 Sep 2014 23:44:35 +0200
> > Subject: futex: Unlock hb->lock in futex_wait_requeue_pi() error path
>
> That's the second time we are bitten by bugs i
On Thu, Sep 11, 2014 at 04:53:38PM -0700, Davidlohr Bueso wrote:
> On Thu, 2014-09-11 at 23:52 +0200, Thomas Gleixner wrote:
> > From: Thomas Gleixner
> > Date: Thu, 11 Sep 2014 23:44:35 +0200
> > Subject: futex: Unlock hb->lock in futex_wait_requeue_pi() error path
>
> That's the second time we
On Thu, 2014-09-11 at 23:52 +0200, Thomas Gleixner wrote:
> From: Thomas Gleixner
> Date: Thu, 11 Sep 2014 23:44:35 +0200
> Subject: futex: Unlock hb->lock in futex_wait_requeue_pi() error path
That's the second time we are bitten by bugs in when requeing, now pi.
We need to reconsider some of ou
On Thu, Sep 11, 2014 at 11:52:02PM +0200, Thomas Gleixner wrote:
> On Thu, 11 Sep 2014, Dave Jones wrote:
>
> > Hit this overnight on Linus tree from yesterday.
> >
> > BUG: sleeping function called from invalid context at
> > include/linux/freezer.h:56
> > in_atomic(): 1, irqs_disabled(): 0, pi
On Thu, 11 Sep 2014, Dave Jones wrote:
> Hit this overnight on Linus tree from yesterday.
>
> BUG: sleeping function called from invalid context at
> include/linux/freezer.h:56
> in_atomic(): 1, irqs_disabled(): 0, pid: 31948, name: trinity-c121
> Preemption disabled at:[] futex_wait_setup+0xb2/
Hit this overnight on Linus tree from yesterday.
BUG: sleeping function called from invalid context at include/linux/freezer.h:56
in_atomic(): 1, irqs_disabled(): 0, pid: 31948, name: trinity-c121
Preemption disabled at:[] futex_wait_setup+0xb2/0x140
CPU: 0 PID: 31948 Comm: trinity-c121 Not taint
6 matches
Mail list logo
