On 07/08/2013 07:12 AM, Jan Kara wrote:
Hum, so it's interesting that ecryptfs_lookup() WARN_ON() didn't trigger but ext4 one did. Strangely enough I don't see a place in the call chain where irqs could get disabled. Can you maybe trace using irq tracing at which point exactly do we disable interrupts?
I'm not familiar with irq tracing, but I traced it as far as a function pointer in a macro at fs/ecryptfs/keystore.c:840 then tried blacklisting the aesni_intel module and I haven't been able to reproduce it since.
At this point I would be interested if anyone else can reproduce it on another Intel Ivy Bridge system with aesni and Linux 3.10:
1. Setup an ecryptfs mount over an ext4 file system 2. Cause a program running inside ecryptfs mount to core dump Thanks, Dustin Lundquist -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
