From: Andrew Morton <akpm@linux-foundation.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Alex Kelly <alex.page.kelly@gmail.com>,
Andi Kleen <andi@firstfloor.org>, Cong Wang <amwang@redhat.com>,
Denys Vlasenko <vda.linux@googlemail.com>,
Jiri Moskovcak <jmoskovc@redhat.com>,
Neil Horman <nhorman@tuxdriver.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] coredump: add support for %d=__get_dumpable() in core name
Date: Thu, 13 Sep 2012 15:25:59 -0700 [thread overview]
Message-ID: <20120913152559.d0a9ade0.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120913172817.GA11337@redhat.com>
On Thu, 13 Sep 2012 19:28:17 +0200
Oleg Nesterov <oleg@redhat.com> wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=787135
Needs a RH bugzilla account, so no Reported-by: for you!
> Some coredump handlers want to create a core file in a way compatible
> with standard behavior. Standard behavior with fs.suid_dumpable = 2
> is to create core file with uid=gid=0. However, there was no way for
> coredump handler to know that the process being dumped was suid'ed.
>
> This patch adds the new %d specifier for format_corename() which
> simply reports __get_dumpable(mm->flags), this is compatible with
> /proc/sys/fs/suid_dumpable we already have.
Please prepare an update to Documentation/sysctl/kernel.txt:core_pattern?
next prev parent reply other threads:[~2012-09-13 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 17:28 [PATCH -mm] coredump: add support for %d=__get_dumpable() in core name Oleg Nesterov
2012-09-13 18:01 ` Neil Horman
2012-09-13 22:25 ` Andrew Morton [this message]
2012-09-14 12:30 ` [PATCH -mm] coredump-add-support-for-%d=__get_dumpable-in-core-name-fix Oleg Nesterov
2012-09-14 12:43 ` [PATCH] coredump: use SUID_DUMPABLE_ENABLED rather than hardcoded 1 Oleg Nesterov
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=20120913152559.d0a9ade0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alex.page.kelly@gmail.com \
--cc=amwang@redhat.com \
--cc=andi@firstfloor.org \
--cc=jmoskovc@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=oleg@redhat.com \
--cc=vda.linux@googlemail.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