Re: [PATCH v3 3/3] sched: BUG when stack end location is over written

2014-09-14 Thread Michael Ellerman
On Fri, 2014-09-12 at 12:58 +0200, Mike Galbraith wrote: > On Fri, 2014-09-12 at 10:44 +0100, Aaron Tomlin wrote: > > On Fri, Sep 12, 2014 at 02:06:57PM +1000, Michael Ellerman wrote: > > > On Thu, 2014-09-11 at 16:41 +0100, Aaron Tomlin wrote: > > > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.

Re: [PATCH v3 3/3] sched: BUG when stack end location is over written

2014-09-12 Thread Mike Galbraith
On Fri, 2014-09-12 at 10:44 +0100, Aaron Tomlin wrote: > On Fri, Sep 12, 2014 at 02:06:57PM +1000, Michael Ellerman wrote: > > On Thu, 2014-09-11 at 16:41 +0100, Aaron Tomlin wrote: > > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > > > index a285900..2a8280a 100644 > > > --- a/lib/Kconfig

Re: [PATCH v3 3/3] sched: BUG when stack end location is over written

2014-09-12 Thread Aaron Tomlin
On Fri, Sep 12, 2014 at 04:04:51PM +1000, Michael Ellerman wrote: > On Thu, 2014-09-11 at 16:41 +0100, Aaron Tomlin wrote: > > Currently in the event of a stack overrun a call to schedule() > > does not check for this type of corruption. This corruption is > > often silent and can go unnoticed. How

Re: [PATCH v3 3/3] sched: BUG when stack end location is over written

2014-09-12 Thread Aaron Tomlin
On Fri, Sep 12, 2014 at 02:06:57PM +1000, Michael Ellerman wrote: > On Thu, 2014-09-11 at 16:41 +0100, Aaron Tomlin wrote: > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > > index a285900..2a8280a 100644 > > --- a/lib/Kconfig.debug > > +++ b/lib/Kconfig.debug > > @@ -824,6 +824,18 @@ config

Re: [PATCH v3 3/3] sched: BUG when stack end location is over written

2014-09-11 Thread Michael Ellerman
On Thu, 2014-09-11 at 16:41 +0100, Aaron Tomlin wrote: > Currently in the event of a stack overrun a call to schedule() > does not check for this type of corruption. This corruption is > often silent and can go unnoticed. However once the corrupted > region is examined at a later stage, the outcome

Re: [PATCH v3 3/3] sched: BUG when stack end location is over written

2014-09-11 Thread Michael Ellerman
On Thu, 2014-09-11 at 16:41 +0100, Aaron Tomlin wrote: > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index a285900..2a8280a 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -824,6 +824,18 @@ config SCHEDSTATS > application, you can say N to avoid the very slight over

[PATCH v3 3/3] sched: BUG when stack end location is over written

2014-09-11 Thread Aaron Tomlin
Currently in the event of a stack overrun a call to schedule() does not check for this type of corruption. This corruption is often silent and can go unnoticed. However once the corrupted region is examined at a later stage, the outcome is undefined and often results in a sporadic page fault which