From: "Jan Beulich" <JBeulich@novell.com>
To: xen-devel@lists.xensource.com
Subject: user mode access to kernel memory
Date: Fri, 29 Jan 2010 10:12:29 +0000 [thread overview]
Message-ID: <4B62C29D020000780002CB4B@vpn.id2.novell.com> (raw)
Tools like crash want to read /proc/mem to get access to RAM. This isn't
allowed under Xen due to the physical/machine address spaces being
distinct. I wonder, however, why this also isn't permitted through
privcmd (or really, why direct_remap_pfn_range() rejects DOMID_SELF,
but permits the resolved domain ID to be passed).
Thanks, Jan
reply other threads:[~2010-01-29 10:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B62C29D020000780002CB4B@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).