> Would you be able to 'git bisect' on your system with Linus'es > linux-2.6.git tree from commit 9fe6206f400646a (v2.6.35) to HEAD at > v2.6.36-rc6 to help us pinpoint which commit the breakage was > introduced..? It's tedious, but I can, HOWEVER... any advice avoiding false positives from https://bugzilla.kernel.org/show_bug.cgi?id=16275 introduced in 74450be123b6f3cb480c358a056be398cce6aa6e and fixed in 2c7d46ec192e4f2b350f67a0e185b9bce646cd6b? I suppose I could cherry-pick the latter when in the vulnerable range... -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
