lkml.org 
[lkml]   [2012]   [Apr]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH][REGRESSION] panic: fix stack dump print on direct call to panic()
    On Mon, 09 Apr 2012 11:34:48 -0700
    Andi Kleen <ak@linux.intel.com> wrote:

    > > The proper way to resolve the problem that original commit tried to
    > > solve is to avoid printing a stack dump from panic() when the either
    > > of the following conditions is true:
    > >
    > > 1) TAINT_DIE has been set (this is done by oops_end())
    > > This indicates and oops has already been printed.
    > > 2) oops_in_progress> 1
    > > This guards against the rare case where panic() is invoked
    > > a second time, or in between oops_begin() and oops_end()
    >
    > Oops. I guess can just revert it for now. Thanks for catching, Jason.

    You're suggesting a revert of 6e6f0a1f0, but Jason is suggesting that
    it be repaired. Confused.


    \
     
     \ /
      Last update: 2012-04-10 21:23    [W:0.019 / U:32.996 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site