> Christain, let's chat about testing at LSF - I was looking at this too > because we thought it was a ktest update that broke at first, but if we > can get you using the automated test infrastructure I built this could > get caught before hitting -next I already do automated testing. This specific error depends on a new config option CONFIG_BLK_DEV_WRITE_MOUNTED which wasn't reflected in my test matrix. I've fixed that now. But I'm always happy to have the tree integrated with other automated testing as well!
