On Wed, Jun 20, 2018 at 04:05:13PM -0400, Steven Rostedt wrote:
>
> Peter, can you ack this.
>
> On Thu, 26 Apr 2018 21:11:00 -0700
> Joel Fernandes wrote:
>
> > I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
> > CONFIG_PREEMPTIRQ_EVENTS=y.
> >
> > $ echo 1 >
On Wed, Jun 20, 2018 at 04:05:13PM -0400, Steven Rostedt wrote:
>
> Peter, can you ack this.
>
> On Thu, 26 Apr 2018 21:11:00 -0700
> Joel Fernandes wrote:
>
> > I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
> > CONFIG_PREEMPTIRQ_EVENTS=y.
> >
> > $ echo 1 >
Peter, can you ack this.
On Thu, 26 Apr 2018 21:11:00 -0700
Joel Fernandes wrote:
> I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
> CONFIG_PREEMPTIRQ_EVENTS=y.
>
> $ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
> ---
BTW, the "---" here causes git to
Peter, can you ack this.
On Thu, 26 Apr 2018 21:11:00 -0700
Joel Fernandes wrote:
> I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
> CONFIG_PREEMPTIRQ_EVENTS=y.
>
> $ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
> ---
BTW, the "---" here causes git to
t;
> ---8<---
>
> From: "Joel Fernandes (Google)"
> Date: Tue, 1 May 2018 18:44:39 -0700
> Subject: [PATCH] softirq: reorder trace_softirqs_on to prevent lockdep splat
>
> I'm able to reproduce a lockdep splat with config options:
> CONFIG_P
t;
> ---8<---
>
> From: "Joel Fernandes (Google)"
> Date: Tue, 1 May 2018 18:44:39 -0700
> Subject: [PATCH] softirq: reorder trace_softirqs_on to prevent lockdep splat
>
> I'm able to reproduce a lockdep splat with config options:
> CONFIG_P
oel
---8<---
From: "Joel Fernandes (Google)"
Date: Tue, 1 May 2018 18:44:39 -0700
Subject: [PATCH] softirq: reorder trace_softirqs_on to prevent lockdep splat
I'm able to reproduce a lockdep splat with config options:
CONFIG_PROVE_LOCKING=y,
CON
oel
---8<---
From: "Joel Fernandes (Google)"
Date: Tue, 1 May 2018 18:44:39 -0700
Subject: [PATCH] softirq: reorder trace_softirqs_on to prevent lockdep splat
I'm able to reproduce a lockdep splat with config options:
CONFIG_PROVE_LOCKING=y,
CON
Peter, Ingo or Thomas,
Can you queue this up? Or would you prefer that I take it?
-- Steve
On Tue, 1 May 2018 18:44:39 -0700
Joel Fernandes wrote:
> I'm able to reproduce a lockdep splat with config options:
> CONFIG_PROVE_LOCKING=y,
> CONFIG_DEBUG_LOCK_ALLOC=y and
>
Peter, Ingo or Thomas,
Can you queue this up? Or would you prefer that I take it?
-- Steve
On Tue, 1 May 2018 18:44:39 -0700
Joel Fernandes wrote:
> I'm able to reproduce a lockdep splat with config options:
> CONFIG_PROVE_LOCKING=y,
> CONFIG_DEBUG_LOCK_ALLOC=y and
>
I'm able to reproduce a lockdep splat with config options:
CONFIG_PROVE_LOCKING=y,
CONFIG_DEBUG_LOCK_ALLOC=y and
CONFIG_PREEMPTIRQ_EVENTS=y
$ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
---
[ 26.112609] DEBUG_LOCKS_WARN_ON(current->softirqs_enabled)
[ 26.112636] WARNING: CPU:
I'm able to reproduce a lockdep splat with config options:
CONFIG_PROVE_LOCKING=y,
CONFIG_DEBUG_LOCK_ALLOC=y and
CONFIG_PREEMPTIRQ_EVENTS=y
$ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
---
[ 26.112609] DEBUG_LOCKS_WARN_ON(current->softirqs_enabled)
[ 26.112636] WARNING: CPU:
On Thu, 26 Apr 2018 21:11:00 -0700
Joel Fernandes wrote:
> I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
> CONFIG_PREEMPTIRQ_EVENTS=y.
>
> $ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
> ---
> [ 26.112609]
On Thu, 26 Apr 2018 21:11:00 -0700
Joel Fernandes wrote:
> I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
> CONFIG_PREEMPTIRQ_EVENTS=y.
>
> $ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
> ---
> [ 26.112609] DEBUG_LOCKS_WARN_ON(current->softirqs_enabled)
On Mon, 30 Apr 2018 17:01:04 +
Joel Fernandes wrote:
Tried 4.17-rc3 and see it too. Could be difference in configs? Also, the
> environment is a Qemu system with single CPU 1GB memory. Attached is the
> config.
>
> I think when I had multiple CPUs it was harder to trigger
On Mon, 30 Apr 2018 17:01:04 +
Joel Fernandes wrote:
Tried 4.17-rc3 and see it too. Could be difference in configs? Also, the
> environment is a Qemu system with single CPU 1GB memory. Attached is the
> config.
>
> I think when I had multiple CPUs it was harder to trigger it, but can't
>
On Mon, Apr 30, 2018 at 9:38 AM Steven Rostedt wrote:
> On Thu, 26 Apr 2018 21:11:00 -0700
> Joel Fernandes wrote:
> > I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
> > CONFIG_PREEMPTIRQ_EVENTS=y.
> >
> > $ echo 1 >
On Mon, Apr 30, 2018 at 9:38 AM Steven Rostedt wrote:
> On Thu, 26 Apr 2018 21:11:00 -0700
> Joel Fernandes wrote:
> > I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
> > CONFIG_PREEMPTIRQ_EVENTS=y.
> >
> > $ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
> >
On Thu, 26 Apr 2018 21:11:00 -0700
Joel Fernandes wrote:
> I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
> CONFIG_PREEMPTIRQ_EVENTS=y.
>
> $ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
> ---
> [ 26.112609]
On Thu, 26 Apr 2018 21:11:00 -0700
Joel Fernandes wrote:
> I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
> CONFIG_PREEMPTIRQ_EVENTS=y.
>
> $ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
> ---
> [ 26.112609] DEBUG_LOCKS_WARN_ON(current->softirqs_enabled)
I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
CONFIG_PREEMPTIRQ_EVENTS=y.
$ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
---
[ 26.112609] DEBUG_LOCKS_WARN_ON(current->softirqs_enabled)
[ 26.112636] WARNING: CPU: 0 PID: 118 at
I'm able to reproduce a lockdep splat when CONFIG_PROVE_LOCKING=y and
CONFIG_PREEMPTIRQ_EVENTS=y.
$ echo 1 > /d/tracing/events/preemptirq/preempt_enable/enable
---
[ 26.112609] DEBUG_LOCKS_WARN_ON(current->softirqs_enabled)
[ 26.112636] WARNING: CPU: 0 PID: 118 at
22 matches
Mail list logo