Re: garbled oopsen

Andi Kleen (ak@muc.de)
Thu, 08 May 2003 04:49:28 +0200


Andrew Morton <akpm@digeo.com> writes:

>> Can these be cleaned up in any reasonable way?
>
> It needs some additional spinlock in there. People have moaned for over a
> year, patches have been floating about but nobody has taken the time to
> finish one off and submit it.

I considered it for x86-64 and even implemented it, but never submitted
in fear of deadlocks e.g. when an oops recurses. For this a
spinlock_timeout() would be useful. Print anyways when you cannot get the
lock in a second or two.

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