Re: [2.4.17/18pre] VM and swap - it's really unusable

[Robert Lowery]

>I question this because it is too risky to apply. There is no way any 
>distribution or production system could ever consider applying the 
>preempt kernel and ship it in its next kernel update 2.4. You never know 
>if a driver will deadlock because it is doing a test and set bit busy 
>loop by hand instead of using spin_lock and you cannot audit all the 
>device drivers out there.

Quick question from a kernel newbie.

Could this audit be partially automated by the Stanford Checker? or would
there
be too many false positives from other similar looping code?

-Robert