xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Keir Fraser <keir@xen.org>
Cc: Xen <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xen/xsm: Fix xsm_mmu_* and xsm_update_va_mapping hooks
Date: Tue, 12 Apr 2011 09:29:03 -0400	[thread overview]
Message-ID: <1302614943.2067.5.camel@moss-pluto> (raw)
In-Reply-To: <C9CA0D84.2C926%keir@xen.org>

On Tue, 2011-04-12 at 14:09 +0100, Keir Fraser wrote:
> On 12/04/2011 13:31, "Stephen Smalley" <sds@tycho.nsa.gov> wrote:
> 
> > On Mon, 2011-03-21 at 14:57 -0400, Stephen Smalley wrote:
> >> This is an attempt to properly fix the hypervisor crash previously
> >> described in
> >> http://marc.info/?l=xen-devel&m=128396289707362&w=2
> >> 
> >> In looking into this issue, I think the proper fix is to move the
> >> xsm_mmu_* and xsm_update_va_mapping hook calls later in the callers,
> >> after more validation has been performed and the page_info struct is
> >> readily available, and pass the page_info to the hooks. This patch moves
> >> the xsm_mmu_normal_update, xsm_mmu_machphys_update and
> >> xsm_update_va_mapping hook calls accordingly, and updates their
> >> interfaces and hook function implementations.  This appears to resolve
> >> the crashes for me.  However, as I am not overly familiar with this area
> >> of code, I'd appreciate any feedback or suggestions for improvement.
> >> 
> >> Signed-off-by:  Stephen Smalley <sds@tycho.nsa.gov>
> > 
> > Zero replies after two postings.  Should I retry, abort, or fail?
> > Seriously though - if there is something wrong with this patch, then let
> > me know, and if not, can it get applied sometime?
> 
> Hi Stephen,
> 
> The patch was posted as RFC with no signed-off-by. The patch looks fine to
> me as far as I understand it. Provide a Signed-off-by line and I'll append
> it to the patch description and apply it.

Not to quibble, but I did drop the RFC and added my Signed-off-by when I
posted it the second time (see above).  The original got posted as an
RFC because it was during the 4.1 freeze, and then I reposted the patch
as an actual submission once the tree was branched and unfrozen.

> You can send these kinds of patches without the RFC tag by the way, unless
> you want to give the opportunity for other NSA people to possibly do review
> via the public list.

-- 
Stephen Smalley
National Security Agency

      reply	other threads:[~2011-04-12 13:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 18:57 [PATCH] xen/xsm: Fix xsm_mmu_* and xsm_update_va_mapping hooks Stephen Smalley
2011-04-12 12:31 ` Stephen Smalley
2011-04-12 13:09   ` Keir Fraser
2011-04-12 13:29     ` Stephen Smalley [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=1302614943.2067.5.camel@moss-pluto \
    --to=sds@tycho.nsa.gov \
    --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).