sfuzz.c (google for it if you don't have it already) used to
run forver (or until I got bored and ctrl-c'd it) as long
as it didn't trigger an oops or the like in 2.6.17
Running it against 2.6.18, I notice that it runs for a while,
and then gets totally wedged. It doesn't respond to any signals,
Dave Jones wrote:
sfuzz D 724EF62A 2828 28717 28691 (NOTLB)
cd69fe98 0082 012d 724ef62a 0001971a 0010 0007
df6d22b0
dfd81080 725bbc5e 0001971a 000cc634 0001 df6d23bc c140e260
0202
de1d5ba0 cd69fea0 de1d5ba0
From: Patrick McHardy [EMAIL PROTECTED]
Date: Thu, 12 Oct 2006 09:46:47 +0200
Looks like unbalanced locking.
Signed-off-by: Patrick McHardy [EMAIL PROTECTED]
Applied and pushed to -stable, thanks Patrick.
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a
