public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: <linux-kernel@vger.kernel.org>, Mateusz Guzik <mguzik@redhat.com>
Cc: <containers@lists.linux-foundation.org>,
	Zhao Lei <zhaolei@cn.fujitsu.com>
Subject: [PATCH 0/2] Make core_pattern support namespace
Date: Wed, 16 Mar 2016 17:23:17 +0800	[thread overview]
Message-ID: <cover.1458119582.git.zhaolei@cn.fujitsu.com> (raw)

We discussed patch titled:
 [PATCH] Make core_pattern support namespace
before.

Above patch can solve half problem of custom core_dump pattern
in container, but there are also another problem that limit
custom core_pattern in container, it is the pipe-type core_pattern
will write core dump into host's filesystem.
(See discussion of that patch for detail)

Now we can solve the second problem by [PATCH 1/2], I send
the origional patch with it.

Zhao Lei (2):
  Run dump pipe in container's namespace
  Make core_pattern support namespace

 arch/x86/kernel/process_32.c  |  5 +--
 arch/x86/kernel/process_64.c  |  5 +--
 fs/coredump.c                 | 79 +++++++++++++++++++++++++------------------
 include/linux/pid_namespace.h |  2 ++
 include/linux/sched.h         |  5 +--
 kernel/fork.c                 | 24 +++++++------
 kernel/pid.c                  |  1 +
 kernel/pid_namespace.c        |  3 ++
 kernel/sysctl.c               | 22 ++++++++----
 9 files changed, 92 insertions(+), 54 deletions(-)

-- 
1.8.5.1

             reply	other threads:[~2016-03-16  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16  9:23 Zhao Lei [this message]
2016-03-16  9:23 ` [PATCH 1/2] Run dump pipe in container's namespace Zhao Lei
2016-03-16  9:43   ` kbuild test robot
2016-03-16  9:23 ` [PATCH 2/2] Make core_pattern support namespace Zhao Lei
2016-03-17  0:57 ` [PATCH 0/2] " Kamezawa Hiroyuki
2016-03-17  2:22   ` Zhao Lei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1458119582.git.zhaolei@cn.fujitsu.com \
    --to=zhaolei@cn.fujitsu.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mguzik@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox