All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] vmdk: fix endianness bugs
Date: Wed, 25 May 2011 09:57:57 +0200	[thread overview]
Message-ID: <4DDCB685.5040505@redhat.com> (raw)
In-Reply-To: <1306277215-17654-2-git-send-email-agraf@suse.de>

Am 25.05.2011 00:46, schrieb Alexander Graf:
> The vmdk code is sloppy when handling the header descriptor during
> creation of an image. Fix all header accesses in the create path to
> either store native endianness or convert it when appropriate.
> 
> Reported-by: Yury Tsarev <ytsarev@novell.com>
> Signed-off-by: Alexander Graf <agraf@suse.de>

Thanks, applied to the block branch.

Kevin

  reply	other threads:[~2011-05-25 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 22:46 [Qemu-devel] [PATCH] ahci: Fix non-NCQ accesses for LBA > 16bits Alexander Graf
2011-05-24 22:46 ` [Qemu-devel] [PATCH] vmdk: fix endianness bugs Alexander Graf
2011-05-25  7:57   ` Kevin Wolf [this message]
2011-05-24 22:58 ` [Qemu-devel] [PATCH] ahci: Fix non-NCQ accesses for LBA > 16bits Alexander Graf

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=4DDCB685.5040505@redhat.com \
    --to=kwolf@redhat.com \
    --cc=agraf@suse.de \
    --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.