On Mon, Apr 11, 2016 at 06:59:23PM +0200, Dario Faggioli wrote:
> On Mon, 2016-04-11 at 17:38 +0100, George Dunlap wrote:
> > On 11/04/16 17:27, Dario Faggioli wrote:
> > >
> > > Commit 94734ab7c3f5 ("xen: sched: close potential races
> > > when switching scheduler to CPUs") buggily replaced a cal
On Mon, 2016-04-11 at 17:38 +0100, George Dunlap wrote:
> On 11/04/16 17:27, Dario Faggioli wrote:
> >
> > Commit 94734ab7c3f5 ("xen: sched: close potential races
> > when switching scheduler to CPUs") buggily replaced a call
> > to pcpu_schedule_lock_irq() with just pcpu_schedule_lock(),
> > caus
On 11/04/16 17:27, Dario Faggioli wrote:
> Commit 94734ab7c3f5 ("xen: sched: close potential races
> when switching scheduler to CPUs") buggily replaced a call
> to pcpu_schedule_lock_irq() with just pcpu_schedule_lock(),
> causing the relevant irq_safe vs. non-irq_safe ASSERT()
> in check_lock() t
Commit 94734ab7c3f5 ("xen: sched: close potential races
when switching scheduler to CPUs") buggily replaced a call
to pcpu_schedule_lock_irq() with just pcpu_schedule_lock(),
causing the relevant irq_safe vs. non-irq_safe ASSERT()
in check_lock() to trigger.
Fix that.
Signed-off-by: Dario Faggiol
