qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Lieven <pl@kamp.de>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] sanitize memory on system reset
Date: Thu, 13 Jun 2013 11:22:56 +0200	[thread overview]
Message-ID: <51B98F70.3070009@suse.de> (raw)
In-Reply-To: <51B96205.4010601@kamp.de>

Hi,

Am 13.06.2013 08:09, schrieb Peter Lieven:
> I was thinking if it would be a good idea to zeroize all memory
> resources on system reset and
> madvise dontneed them afterwards.

The current way of not zeroing memory has led to discovery of some
firmware bugs that we wouldn't have found if QEMU defaulted to zeroing.

> This would avoid system reset attacks
> in case the attacker
> has only access to the console of a vServer but not on the physical host
> and it would shrink
> RSS size of the vServer siginificantly.

Apart from the guest issue Stefan brought up (so far by definition we do
a hard reset, so guests cannot assume soft reset semantics, but we
should keep our options open), would not zeroing while marking pages as
unused be an option? E.g., -reset-memory=DEADBEEF or some other
command-line-specifiable pattern, absence would mean current behavior.

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2013-06-13  9:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  6:09 [Qemu-devel] [RFC] sanitize memory on system reset Peter Lieven
2013-06-13  8:40 ` Stefan Hajnoczi
2013-06-13  8:46   ` Peter Lieven
2013-06-14 11:06     ` Stefan Hajnoczi
2013-06-13  8:51   ` Peter Lieven
2013-06-13 10:55     ` Markus Armbruster
2013-06-13 11:56       ` Anthony Liguori
2013-06-13 12:30         ` Paolo Bonzini
2013-06-14  6:56         ` Christian Borntraeger
2013-06-14  9:44           ` Alexander Graf
2013-06-14 13:43             ` Paolo Bonzini
2013-06-17  7:18               ` Peter Lieven
2013-06-14 16:14             ` H. Peter Anvin
2013-06-13 14:23       ` Peter Lieven
2013-06-13 15:51         ` Markus Armbruster
2013-06-13 19:20           ` Peter Lieven
2013-06-13  9:22 ` Andreas Färber [this message]
2013-06-13  9:33   ` Peter Lieven

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=51B98F70.3070009@suse.de \
    --to=afaerber@suse.de \
    --cc=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).