On 05/22/2014 02:59 AM, Peter Zijlstra wrote:
> On Wed, May 21, 2014 at 10:34:44PM -0400, Sasha Levin wrote:
>> On 05/21/2014 12:49 PM, Peter Zijlstra wrote:
>>> On Wed, May 21, 2014 at 03:19:48PM +0200, Peter Zijlstra wrote:
> On Wed, May 21, 2014 at 09:08:26AM -0400, Sasha Levin wrote:
>>
On Thu, May 22, 2014 at 11:05:40AM +0530, Srikar Dronamraju wrote:
> > diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> > index 927fa33..b5e11c7 100644
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -1154,6 +1156,7 @@ int migrate_swap(struct task_struct *cur, struct
> >
On Wed, May 21, 2014 at 10:34:44PM -0400, Sasha Levin wrote:
> On 05/21/2014 12:49 PM, Peter Zijlstra wrote:
> > On Wed, May 21, 2014 at 03:19:48PM +0200, Peter Zijlstra wrote:
> >> > On Wed, May 21, 2014 at 09:08:26AM -0400, Sasha Levin wrote:
> >>> > > +++ b/kernel/sched/core.c
> >>> > > @@ -1154
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 927fa33..b5e11c7 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -1154,6 +1156,7 @@ int migrate_swap(struct task_struct *cur, struct
> task_struct *p)
> goto out;
>
> trace_sched_swap_numa(
On 05/21/2014 12:49 PM, Peter Zijlstra wrote:
> On Wed, May 21, 2014 at 03:19:48PM +0200, Peter Zijlstra wrote:
>> > On Wed, May 21, 2014 at 09:08:26AM -0400, Sasha Levin wrote:
>>> > > +++ b/kernel/sched/core.c
>>> > > @@ -1154,6 +1156,7 @@ int migrate_swap(struct task_struct *cur, struct
>>> > >
On Wed, May 21, 2014 at 03:19:48PM +0200, Peter Zijlstra wrote:
> On Wed, May 21, 2014 at 09:08:26AM -0400, Sasha Levin wrote:
> > +++ b/kernel/sched/core.c
> > @@ -1154,6 +1156,7 @@ int migrate_swap(struct task_struct *cur, struct
> > task_struct *p)
> > goto out;
> >
> >
On Wed, May 21, 2014 at 09:08:26AM -0400, Sasha Levin wrote:
> On 05/20/2014 09:03 AM, Sasha Levin wrote:
> > On 05/20/2014 07:04 AM, Peter Zijlstra wrote:
> >> > On Mon, May 19, 2014 at 10:05:31PM -0400, Sasha Levin wrote:
> >>> >> ping? It seems to be easy enough to reproduce on -next, I'd be hap
On 05/20/2014 09:03 AM, Sasha Levin wrote:
> On 05/20/2014 07:04 AM, Peter Zijlstra wrote:
>> > On Mon, May 19, 2014 at 10:05:31PM -0400, Sasha Levin wrote:
>>> >> ping? It seems to be easy enough to reproduce on -next, I'd be happy to
>>> >> try
>>> >> debug patches/fixes.
>> >
>> > Does this fu
On 05/20/2014 07:04 AM, Peter Zijlstra wrote:
> On Mon, May 19, 2014 at 10:05:31PM -0400, Sasha Levin wrote:
>> ping? It seems to be easy enough to reproduce on -next, I'd be happy to try
>> debug patches/fixes.
>
> Does this fuzzing you do also include hotplug? If so, does disabling
> that make t
On Mon, May 19, 2014 at 10:05:31PM -0400, Sasha Levin wrote:
> ping? It seems to be easy enough to reproduce on -next, I'd be happy to try
> debug patches/fixes.
Does this fuzzing you do also include hotplug? If so, does disabling
that make this problem go away?
--
To unsubscribe from this list: s
ping? It seems to be easy enough to reproduce on -next, I'd be happy to try
debug patches/fixes.
Thanks,
Sasha
On 05/12/2014 02:25 PM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running the latest -next
> kernel I've stumbled on the following spew:
>
>
Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest -next
kernel I've stumbled on the following spew:
[ 1738.758667] BUG: spinlock recursion on CPU#23, migration/23/328
[ 1738.761291] lock: 0x8801f93b0c30, .magic: dead4ead, .owner:
migration/23/328, .owner_cpu: 23
12 matches
Mail list logo