From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir@xen.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: bogus check in get_page_from_l1e()?
Date: Tue, 08 Mar 2011 11:07:41 +0000 [thread overview]
Message-ID: <4D761C0D0200007800035236@vpn.id2.novell.com> (raw)
Keir,
in the I/O page code path, we have
if ( !iomem_access_permitted(pg_owner, mfn, mfn) )
{
if ( mfn != (PADDR_MASK >> PAGE_SHIFT) ) /* INVALID_MFN? */
MEM_LOG("Non-privileged (%u) attempt to map I/O space %08lx",
pg_owner->domain_id, mfn);
return 0;
}
What is the reason to suppress the warning for the one specific
(PADDR_MASK >> PAGE_SHIFT) MFN value, i.e. where could this
validly come from and hence warrant not to issue the warning?
Also, the message seems to be having the potential of being
misleading (these days at least, but perhaps it always was), as
it clearly is possible for Dom0 to also be denied a mapping here
(and hence the "Non-privileged" can be wrong).
Bottom line question: Should we issue the warning unconditionally,
just stating the domain ID?
Thanks, Jan
next reply other threads:[~2011-03-08 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 11:07 Jan Beulich [this message]
2011-03-08 15:19 ` bogus check in get_page_from_l1e()? Keir Fraser
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=4D761C0D0200007800035236@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=keir@xen.org \
--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).