qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, carnold@suse.com, jcody@redhat.com,
	qemu-stable@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block/vpc: fix get_sector_offset for vpc_read
Date: Mon, 23 Feb 2015 12:10:46 -0500	[thread overview]
Message-ID: <54EB5F16.9090409@redhat.com> (raw)
In-Reply-To: <1424703692-21364-1-git-send-email-pl@kamp.de>

On 2015-02-23 at 10:01, Peter Lieven wrote:
> VHD images contain a bitmap at the beginning of each data block
> to indicate the allocation status of each sector in the data block.
>
> vpc_read currently checks the allocation status of the first sector
> in a data block it is going to read and then assumes the same allocation
> status for the whole remainder of the data block. This might end up
> in incorrect zero sectors if the first sector is unallocated.
>
> To fix this indiciate a sector is allocated as soon as its
> data block has a valid page table index.

Hm, as far as I can see, this patch just removes unused code. How does 
this correspond to the commit message?

Max

> CC: qemu-stable@nongnu.org
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
>   block/vpc.c |   32 --------------------------------
>   1 file changed, 32 deletions(-)
>
> diff --git a/block/vpc.c b/block/vpc.c
> index 46803b1..9a75334 100644
> --- a/block/vpc.c
> +++ b/block/vpc.c
> @@ -376,38 +376,6 @@ static inline int64_t get_sector_offset(BlockDriverState *bs,
>           bdrv_pwrite_sync(bs->file, bitmap_offset, bitmap, s->bitmap_size);
>       }
>   
> -//    printf("sector: %" PRIx64 ", index: %x, offset: %x, bioff: %" PRIx64 ", bloff: %" PRIx64 "\n",
> -//	sector_num, pagetable_index, pageentry_index,
> -//	bitmap_offset, block_offset);
> -
> -// disabled by reason
> -#if 0
> -#ifdef CACHE
> -    if (bitmap_offset != s->last_bitmap)
> -    {
> -	lseek(s->fd, bitmap_offset, SEEK_SET);
> -
> -	s->last_bitmap = bitmap_offset;
> -
> -	// Scary! Bitmap is stored as big endian 32bit entries,
> -	// while we used to look it up byte by byte
> -	read(s->fd, s->pageentry_u8, 512);
> -	for (i = 0; i < 128; i++)
> -	    be32_to_cpus(&s->pageentry_u32[i]);
> -    }
> -
> -    if ((s->pageentry_u8[pageentry_index / 8] >> (pageentry_index % 8)) & 1)
> -	return -1;
> -#else
> -    lseek(s->fd, bitmap_offset + (pageentry_index / 8), SEEK_SET);
> -
> -    read(s->fd, &bitmap_entry, 1);
> -
> -    if ((bitmap_entry >> (pageentry_index % 8)) & 1)
> -	return -1; // not allocated
> -#endif
> -#endif
> -
>       return block_offset;
>   }
>   

  reply	other threads:[~2015-02-23 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 15:01 [Qemu-devel] [PATCH] block/vpc: fix get_sector_offset for vpc_read Peter Lieven
2015-02-23 17:10 ` Max Reitz [this message]
2015-02-24  6:41   ` [Qemu-devel] [Qemu-stable] " 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=54EB5F16.9090409@redhat.com \
    --to=mreitz@redhat.com \
    --cc=carnold@suse.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=stefanha@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 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).