[lkml]   [2002]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Preempt note in the logs

On 24 Aug 2002, Robert Love wrote:
> On Sat, 2002-08-24 at 14:01, Thunder from the hill wrote:
> > Do you think it's useful to temporarily put a lock counter into struct
> > task (TEMPORARILY, Linus, temporarily!) and check that as well? Maybe that
> > will point us something.
> There already is, it is called preempt_count.

Yes, I know about this one. But you never know how many different-type
locks you'll find. In the worst case there's a kernelful of crap around,
you know.

> A lock trace would be helpful here. But since I know normal kernel code
> is not suspect, all these users need to do is find which oddball module
> or patch they are using... e.g. watch it be nvidia.

Hey, it's not all the world that is bad. I'm not just fixed on this bug
here. I'm suggesting this as a serious finder for broken things which
could be used all over the place.

(Of course my (and possibly even your) great dream is that we can find
these things before we boot the broken kernel. Good old
and a few AI might help here.)

--./../...-/. -.--/---/..-/.-./..././.-../..-. .---/..-/.../- .-
--/../-./..-/-/./--..-- ../.----./.-../.-.. --./../...-/. -.--/---/..-
.- -/---/--/---/.-./.-./---/.--/.-.-.-

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

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