All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Juan Quintela <quintela@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Liran Schour <LIRANS@il.ibm.com>,
	Pierre Riteau <Pierre.Riteau@irisa.fr>
Subject: [Qemu-devel] Re: [PATCH] vmstate: Avoid seeking
Date: Wed, 02 Dec 2009 12:14:41 +0100	[thread overview]
Message-ID: <4B164C21.3040406@siemens.com> (raw)
In-Reply-To: <m3eindn11u.fsf@neno.neno>

Juan Quintela wrote:
> Jan Kiszka <jan.kiszka@web.de> wrote:
>> Seeking on vmstate save/load does not work if the underlying file is a
>> stream. We could try to make all QEMUFile* forward-seek-aware, but first
>> attempts in this direction indicated that it's saner to convert the few
>> qemu_fseek-on-vmstates users to plain reads/writes.
>>
>> This fixes various subtle vmstate corruptions where unused fields were
>> involved.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> 
> Something changed lately.  This used to work, and I also waste^spend
> yesterday trying to understand why it was failing to me.

I'm quite sure it never really worked. Maybe the bug was just papered over.

> 
> I am splitting the patch in virtio-net and savevm parts.  (In my tree
> virtio-net don't use fseek anymore).

OK, then I will drop this patch from my queue. BTW, where is your tree
hosted?

> 
> Thanks for finding the bug.
> 
> Later, Juan.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2009-12-02 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 23:38 [Qemu-devel] [PATCH] vmstate: Avoid seeking Jan Kiszka
2009-12-02  3:24 ` Ryan Harper
2009-12-02 10:05 ` [Qemu-devel] " Juan Quintela
2009-12-02 11:14   ` Jan Kiszka [this message]
2009-12-02 11:24     ` Juan Quintela

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=4B164C21.3040406@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=LIRANS@il.ibm.com \
    --cc=Pierre.Riteau@irisa.fr \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 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.