We found the issue -- I think xnox is going to report it via proper channels. But basically it's this:
<mwhudson> sizeof(dev_t) = 4 sizeof(__kernel_old_dev_t) = 8
This makes the kernel's loop_info 8 bytes bigger than klibc's and so the kernel is writing past the end of the loopinfo on the stack, which until now has avoided causing problems by sheer luck.
We found the issue -- I think xnox is going to report it via proper channels. But basically it's this:
<mwhudson> sizeof(dev_t) = 4 sizeof( __kernel_ old_dev_ t) = 8
This makes the kernel's loop_info 8 bytes bigger than klibc's and so the kernel is writing past the end of the loopinfo on the stack, which until now has avoided causing problems by sheer luck.