On Thu, Sep 04, 2014 at 03:50:24PM +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
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
On Thu, Sep 04, 2014 at 05:32:31PM +0200, Peter Zijlstra wrote:
On Thu, Sep 04, 2014 at 03:50:24PM +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.