Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753202AbaLARKj (ORCPT ); Mon, 1 Dec 2014 12:10:39 -0500 Received: from foss-mx-na.foss.arm.com ([217.140.108.86]:42662 "EHLO foss-mx-na.foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752817AbaLARKi (ORCPT ); Mon, 1 Dec 2014 12:10:38 -0500 Date: Mon, 1 Dec 2014 17:10:37 +0000 From: Will Deacon To: Linus Torvalds Cc: Dave Jones , Andy Lutomirski , Don Zickus , Thomas Gleixner , Linux Kernel , the arch/x86 maintainers , Peter Zijlstra Subject: Re: frequent lockups in 3.18rc4 Message-ID: <20141201171036.GH18466@arm.com> References: <20141118215540.GD35311@redhat.com> <20141119021902.GA14216@redhat.com> <20141119145902.GA13387@redhat.com> <546D0530.8040800@mit.edu> <20141120152509.GA5412@redhat.com> <20141125122217.GA15280@arm.com> <20141201114854.GB18466@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 01, 2014 at 05:05:06PM +0000, Linus Torvalds wrote: > On Mon, Dec 1, 2014 at 3:48 AM, Will Deacon 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/