On 28 January 2015 at 15:24, Mark Brown <broo...@kernel.org> wrote: > For at least the past couple of days tests of libhugetlbfs have been > hanging on mustang in the mlock test running ARMv8 defconfig with both > 32 bit and 64 bit userspace - after the mprotect test (the one before > it) we get no console output for several hours so it appears that the > test has deadlocked. The tail of the log is: > > | find_path (2M: 64): PASS > | unlinked_fd (2M: 64): PASS > | readback (2M: 64): PASS > | truncate (2M: 64): PASS > | shared (2M: 64): PASS > | mprotect (2M: 64): PASS > > and then a timeout. > > This may be a generic bug but my ability to run these tests on other > platforms with huge page support using the infrastructure I'm using is > limited so I've not been able to test elsewhere and confirm.
I've reproduced this on Juno, it looks like hugtlb_fault is being called repeatedly in the mlock test. I'll investigate further. Cheers, -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
