On Mon, Dec 01, 2014 at 05:05:06PM +0000, Linus Torvalds wrote: > On Mon, Dec 1, 2014 at 3:48 AM, Will Deacon <will.dea...@arm.com> wrote: > > so for some bizarre reason, child1 (27912) managed to execve oom_score > > from /proc. > > That sounds like you have a binfmt that accepts crap. Possibly > ARM-specific, although more likely it's just a misc script. > > > We can see the child that did the execve has somehow gained its own > > child process (27921) that we're unable to backtrace. I can't see any > > clone/fork syscalls in the log for 27912. > > Well, it wouldn't be trinity any more, it would likely be some execve > script (think "/bin/sh", except likely through binfmt_misc). > > Do you have anything in /proc/sys/fs/binfmt_misc? I don't see anything > else that would trigger it.
So I don't even have binfmt-misc compiled in. The two handlers I have are BINFMT_ELF and BINFMT_SCRIPT, but they both check for headers that we won't get back from oom_score afaict. > This doesn't really look anything like DaveJ's issue, but who knows.. It's the only lockup I'm seeing on arm64 with trinity, but I agree that it's not very helpful. Will -- 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/