Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752338AbbLIIOt (ORCPT ); Wed, 9 Dec 2015 03:14:49 -0500 Received: from cn.fujitsu.com ([59.151.112.132]:31056 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751779AbbLIIOr (ORCPT ); Wed, 9 Dec 2015 03:14:47 -0500 X-IronPort-AV: E=Sophos;i="5.20,346,1444665600"; d="scan'208";a="1366399" Message-ID: <5667E113.5020506@cn.fujitsu.com> Date: Wed, 9 Dec 2015 16:06:43 +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> <5667C1BC.7070204@cn.fujitsu.com> <87oae0dtd8.fsf@x220.int.ebiederm.org> In-Reply-To: <87oae0dtd8.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: BB56141887D5.AA220 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: 2184 Lines: 61 On 12/09/2015 02:32 PM, Eric W. Biederman wrote: > Dongsheng Yang writes: > >> 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? > > The kernel rules say if there is a behavior someone depends on and that > behavior changes and breaks userspace that is a regression and it is not > allowed. > > As developers we try not to create regressions. But some days it > requires someone testing/using the functional enough to catdch an issue. > > That said the real issue you are likely to run into when developing this > as part of docker is that docker doesn't get to own the core pattern. > It doesn't make sense for any one application to, as it is a kernel wide > setting. Agreed. > To have different app or container specific policies for core > dumping likely requires either solving the problems I mentioned with > containers or in userspace a solution so there can be an > /etc/core_pattern.d/ with different configuration and different scripts > that somehow know how to select which core files they want and dump them > sanely. We would try to solve the problems you mentioned, but sound not easy. Anyway, I need to read some old discussion at first I think. Thanx Yang > > Eric > > > -- 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/