From: "Marc Marí" <markmb@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] fw_cfg DMA security
Date: Fri, 23 Oct 2015 11:49:49 +0200 [thread overview]
Message-ID: <20151023114949.76bdaf6a@markmb_rh> (raw)
In-Reply-To: <1445583386.13733.134.camel@redhat.com>
On Fri, 23 Oct 2015 08:56:26 +0200
Gerd Hoffmann <kraxel@redhat.com> wrote:
> Hi,
>
> > One complication I thought of was that it might be tricky to deal
> > with the implications of allowing this DMA to specify any old
> > address to fill with fw_cfg data.
> >
> > So, for example, since Red Hat is working on SMM. Would a DMA to
> > SMRAM be protected?
> >
> > I haven't watched the fw_cfg DMA discussion too closely, but has
> > this been thought about?
>
> Yes. That problem isn't new and it isn't specific to fw_cfg. You
> also don't want grant dma access to smram/tseg to your ide/sata/scsi
> controller or NIC.
>
> > One idea I had was that near the end of the firmware boot, the
> > firmware could trigger fw_cfg in QEMU to stop supporting DMA until a
> > reset.
>
> Should not be needed. We have address spaces in qemu, and the
> smram/tseg regions are explicitly excluded (when enabled) from
> dma-able memory.
>
> mark: when writing a fw_cfg_dma tests it is a good idea to add a
> testcase for this, so make sure this works as intended and to avoid
> security-sensitive regressions.
Noted, thanks
Marc
> cheers,
> Gerd
>
>
prev parent reply other threads:[~2015-10-23 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 6:27 [Qemu-devel] fw_cfg DMA security Jordan Justen
2015-10-23 6:56 ` Gerd Hoffmann
2015-10-23 7:29 ` Paolo Bonzini
2015-10-23 9:49 ` Marc Marí [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=20151023114949.76bdaf6a@markmb_rh \
--to=markmb@redhat.com \
--cc=jordan.l.justen@intel.com \
--cc=kraxel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.