> Well, the kernel Debian stable kernel, so it should be handled > really handled by the Debian distro bugzilla. > (Otherwise, please try more recent, ideally 3.12 stable kernel. > Using loop devices is quite common and I do not think there are recent > problems here.) That's why I submitted it there. But every single party that is involved in kernel development or support likes to point the finger at someone else without bothering to attempt reproducing. That's been my past experience, which is why I'm trying multiple avenues for support here. > Also try use loop directly. Does mkfs works ok? What is the underlying > filesystem and mount parameters (on which image resides)? Just tried a plain loopback device. It is a tad slower than doing mkfs directly on the file, but nothing close to the issues with the luks loopback. > If it "locks" paste kernel trace to bugzilla (through sysrq, > "echo t > /proc/sysrq-trigger" and see syslog.) > > (It seems to me more like problem with loop device or combination > than with dmcrypt. Anyway, if you are able to reproduce it on upstream > kernel, add device mapper devel list to cc - dm-devel@xxxxxxxxxx) Yeah, that's where 99% of bug reporters stop... tim _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
