From: Jason Baron <jbaron@redhat.com>
To: mcgrathr@google.com
Cc: qemu-devel@nongnu.org, akpm@linux-foundation.org, avi@redhat.com,
linux-kernel@vger.kernel.org
Subject: [Qemu-devel] [PATCH 0/2] core dump: re-purpose VM_ALWAYSDUMP to user controlled VM_DONTDUMP
Date: Wed, 7 Mar 2012 12:00:46 -0500 [thread overview]
Message-ID: <cover.1331137504.git.jbaron@redhat.com> (raw)
Hi,
The motivation for this change was that I was looking at a way for a qemu-kvm
process, to exclude the guest memory from its core dump, which can be quite
large. There are already a number of filter flags in
/proc/<pid>/coredump_filter, however, these allow one to specify 'types' of
kernel memory, not specific address ranges (which is needed in this case).
Since there are no more vma flags available, the first patch eliminates the
need for the 'VM_ALWAYSDUMP' flag. The flag is used internally by the kernel to
mark vdso and vsyscall pages. However, it is simple enough to check if a vma
covers a vdso or vsyscall page without the need for this flag.
The second patch then replaces the 'VM_ALWAYSDUMP' flag with a new
'VM_DONTDUMP' flag, which can be set by userspace using new madvise flags:
'MADV_DONTDUMP', and unset via 'MADV_DUMP'. The core dump filters continue to
work the same as before unless 'MADV_DONTDUMP' is set on the region.
The qemu code which implements this features is at:
http://people.redhat.com/~jbaron/qemu-dump/qemu-dump.patch
In my testing the qemu core dump shrunk from 383MB -> 13MB with this patch.
I also believe that the 'MADV_DONTDUMP' flag might be useful for security
sensitive apps, which might want to select which areas are dumped.
Thanks,
-Jason
Jason Baron (2):
core dump: drop VM_ALWAYSDUMP flag
core dump: add a new VM_DONTDUMP flag
arch/arm/kernel/process.c | 2 +-
arch/hexagon/kernel/vdso.c | 3 +--
arch/mips/kernel/vdso.c | 3 +--
arch/powerpc/kernel/vdso.c | 3 +--
arch/s390/kernel/vdso.c | 3 +--
arch/sh/kernel/vsyscall/vsyscall.c | 3 +--
arch/tile/mm/elf.c | 3 +--
arch/unicore32/kernel/process.c | 2 +-
arch/x86/um/mem_32.c | 8 --------
arch/x86/um/vdso/vma.c | 3 +--
arch/x86/vdso/vdso32-setup.c | 11 ++---------
arch/x86/vdso/vma.c | 3 +--
fs/binfmt_elf.c | 23 +++++++++++++++++++++--
include/asm-generic/mman-common.h | 3 +++
include/linux/mm.h | 2 +-
mm/madvise.c | 8 ++++++++
mm/memory.c | 8 +-------
17 files changed, 46 insertions(+), 45 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-03-07 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 17:00 Jason Baron [this message]
2012-03-07 17:00 ` [Qemu-devel] [PATCH 1/2] core dump: drop VM_ALWAYSDUMP flag Jason Baron
2012-03-07 17:59 ` Roland McGrath
2012-03-07 18:50 ` Jason Baron
2012-03-07 19:43 ` Roland McGrath
2012-03-07 21:19 ` Jason Baron
2012-03-07 21:26 ` Chris Metcalf
2012-03-07 21:36 ` Jason Baron
2012-03-07 21:41 ` Roland McGrath
2012-03-07 17:00 ` [Qemu-devel] [PATCH 2/2] core dump: add a new VM_DONTDUMP flag Jason Baron
2012-03-07 22:30 ` [Qemu-devel] [PATCH 0/2] core dump: re-purpose VM_ALWAYSDUMP to user controlled VM_DONTDUMP Andrew Morton
2012-03-08 1:32 ` Jason Baron
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.1331137504.git.jbaron@redhat.com \
--to=jbaron@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrathr@google.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).