lkml.org 
[lkml]   [2000]   [Jul]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH #2] console lock grabbed too early in printk...
    > > To solve this, I see two main strategies that are usable:
    > > 1. Count printk's that cannot be used due to recursive entries. On the
    > > next successful printk, indicate that some printk's were lost.
    > > 2. kmalloc(GFP_ATOMIC) a temporary buffer, and try our damnest to get the
    > > message through to the user/kernel developer.
    >
    > 3: If a deadlock is detected, just jam the message out somehow and
    > then BUG(). That's good enough!

    If you are jamming the message out anyways, you might as well continue on
    and run... what's the difference? You need a buffer either way...

    -Chris


    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:57    [W:2.532 / U:0.184 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site