From: Jeff Moyer <jmoyer@redhat.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-nvdimm@ml01.01.org, Ingo Molnar <mingo@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
Matthew Wilcox <matthew.r.wilcox@intel.com>
Subject: Re: [PATCH 0/2] Add explicit coredump filtering for DAX mappings
Date: Thu, 15 Oct 2015 16:01:30 -0400 [thread overview]
Message-ID: <x49pp0fgaud.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <1444084417-19192-1-git-send-email-ross.zwisler@linux.intel.com> (Ross Zwisler's message of "Mon, 5 Oct 2015 16:33:35 -0600")
Ross Zwisler <ross.zwisler@linux.intel.com> writes:
> Add two new flags to the existing coredump mechanism for ELF files to allow
> us to explicitly filter DAX mappings. This is desirable because DAX
> mappings, like hugetlb mappings, have the potential to be very large.
>
> The coredump code relies on get_user_page() to populate the coredump file
> with the appropriate data, and for DAX mappings this currently fails. This
> results in a hole being placed in the coredump file, so you end up reading
> back zeros. Once the get_user_pages() patch series from Dan Williams [1]
> is merged, DAX core dumps will give real data.
>
> I have a patch ready for core(5) to update the documentation on the new
> filtering flags. I'll send it out once this gets merged.
Looks straight-forward.
Acked-by: Jeff Moyer <jmoyer@redhat.com>
prev parent reply other threads:[~2015-10-15 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 22:33 Ross Zwisler
2015-10-05 22:33 ` [PATCH 1/2] coredump: add DAX filtering for ELF coredumps Ross Zwisler
2015-10-05 22:33 ` [PATCH 2/2] coredump: add DAX filtering for FDPIC " Ross Zwisler
2015-10-13 22:54 ` [PATCH 0/2] Add explicit coredump filtering for DAX mappings Ross Zwisler
2015-10-15 20:01 ` Jeff Moyer [this message]
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=x49pp0fgaud.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=matthew.r.wilcox@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ross.zwisler@linux.intel.com \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome