[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <542E2D56.6090007@oracle.com>
Date: Fri, 03 Oct 2014 01:00:06 -0400
From: Sasha Levin <sasha.levin@...cle.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
CC: Hugh Dickins <hughd@...gle.com>, Dave Jones <davej@...hat.com>,
Al Viro <viro@...iv.linux.org.uk>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Rik van Riel <riel@...hat.com>,
Ingo Molnar <mingo@...hat.com>,
Michel Lespinasse <walken@...gle.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Mel Gorman <mgorman@...e.de>
Subject: Re: pipe/page fault oddness.
On 10/02/2014 12:10 PM, Linus Torvalds wrote:
> On Thu, Oct 2, 2014 at 8:04 AM, Sasha Levin <sasha.levin@...cle.com> wrote:
>> >
>> > I have a new one for you. I know it doesn't say "numa" anywhere, but I
>> > haven't ever seen that trace before so I'll just go ahead and blame it
>> > on your patch...
> Fair enough, but the oops doesn't really give even a hint of what
> could be wrong.
>
> The stack is clearly too deep:
>
> Thread overran stack, or stack corrupted
> task.ti: ffff880dba2ec000
> RSP: ffff880dba2ebf48
>
> but my patch shouldn't have added any deeper call-chains anywhere.
For the record, I tweaked the environment to put some more pressure on the
scheduler and found out what broke (which is not related to this thread at
all).
For the curious ones: https://lkml.org/lkml/2014/10/3/5
Thanks,
Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists