The memory leak seems to be sorted. The future domain/scsi stuff isn't going
to get solved that rapidly. In 2.3.18 the scsi layer is getting cleaned up
and tidied. That should eventually reveal how a command is getting
queued in some cases when its not allowed to be.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/