Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752080AbbLIGBJ (ORCPT ); Wed, 9 Dec 2015 01:01:09 -0500 Received: from cn.fujitsu.com ([59.151.112.132]:46325 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751134AbbLIGBH (ORCPT ); Wed, 9 Dec 2015 01:01:07 -0500 X-IronPort-AV: E=Sophos;i="5.20,346,1444665600"; d="scan'208";a="1361030" Message-ID: <5667C1BC.7070204@cn.fujitsu.com> Date: Wed, 9 Dec 2015 13:53:00 +0800 From: Dongsheng Yang User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: "Eric W. Biederman" CC: Shayan Pooya , , , Richard Weinberger , Subject: Re: piping core dump to a program escapes container References: <56679161.303@cn.fujitsu.com> <56679399.6080306@cn.fujitsu.com> <876108fgfq.fsf@x220.int.ebiederm.org> In-Reply-To: <876108fgfq.fsf@x220.int.ebiederm.org> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.167.226.66] X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner-ID: ED71D41890E3.AA21D X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: yangds.fnst@cn.fujitsu.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1814 Lines: 62 On 12/09/2015 11:29 AM, Eric W. Biederman wrote: > Dongsheng Yang writes: > [...] > There has not yet been an obvious namespace in which to stick > core_pattern, and even worse exactly how to appropriate launch a process > in a container has not been figured out. > > If those tricky problems can be solved we can have a core_pattern in a > container. What we have now is the best we have been able to figure out > so far. Thanx Eric, but if I want to make docker works rely on this behaviour, is that reliable? I mean, I want to make a docker container to dump the core file to a specified path in host by a pipe way. But I am afraid this behaviour would be changed later. Any suggestion? Yang > > Eric > > >> >> Yang >>> >>> Yang >>>> >>>> Currently, I work around this issue by detecting that the process is >>>> crashing from a container (by comparing the namespace pid to the >>>> global pid) and refuse to dump the core if it is from a container. >>>> >>>> Tested on Ubuntu (kernel 3.16) and Fedora (kernel 4.1). >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe cgroups" in >>>> the body of a message to majordomo@vger.kernel.org >>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>>> >>> >>> >>> >>> -- >>> 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/ >>> . >>> > > > . > -- 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/