Hello,
we discovered this kernel panic [1] in 2.6.36. Apparently, commit
a1c6c5698d53db4c47a25c3a8d11731a4d7b8370 was supposed to fix it, but
never made it to 2.6.36(.1). Can this please be queued up for the next
stable kernel? This is a pretty serious issue and can reproducibly crash
the kernel.
This was mentioned at [2], but nothing more happened. Added some ext4
guys to CC.
Regards
Thomas
[1] http://richard.qasl.de/panic.JPG
[2] http://lkml.org/lkml/2010/11/20/64