qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] fix sector overflow for scsi disks >1TB large
Date: Mon, 26 Jan 2009 17:42:09 -0500	[thread overview]
Message-ID: <20090126174209.1690ef05@bree.surriel.com> (raw)

Sector numbers can overflow on a virtual scsi disk of over 1TB
in size.  Qemu's bdrv_read expects an int64_t, so fix the overflow
by going to that data type.

Also clip capacity to 2TB instead of returning "capacity modulo 2TB".

Signed-off-by: Rik van Riel <riel@redhat.com>

Index: trunk/hw/scsi-disk.c
===================================================================
--- trunk/hw/scsi-disk.c	(revision 6451)
+++ trunk/hw/scsi-disk.c	(working copy)
@@ -50,7 +50,7 @@
     /* ??? We should probably keep track of whether the data trasfer is
        a read or a write.  Currently we rely on the host getting it right.  */
     /* Both sector and sector_count are in terms of qemu 512 byte blocks.  */
-    int sector;
+    uint64_t sector;
     int sector_count;
     /* The amounnt of data in the buffer.  */
     int buf_len;
@@ -731,6 +731,9 @@
         /* Returned value is the address of the last sector.  */
         if (nb_sectors) {
             nb_sectors--;
+            /* Clip to 2TB, instead of returning capacity modulo 2TB. */
+            if (nb_sectors > UINT_MAX)
+                nb_sectors = UINT_MAX;
             outbuf[0] = (nb_sectors >> 24) & 0xff;
             outbuf[1] = (nb_sectors >> 16) & 0xff;
             outbuf[2] = (nb_sectors >> 8) & 0xff;

             reply	other threads:[~2009-01-26 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 22:42 Rik van Riel [this message]
2009-01-26 23:55 ` [Qemu-devel] [PATCH] fix sector overflow for scsi disks >1TB large Jamie Lokier
2009-01-27 15:49   ` Rik van Riel
  -- strict thread matches above, loose matches on Subject: below --
2009-01-27 15:51 Rik van Riel

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=20090126174209.1690ef05@bree.surriel.com \
    --to=riel@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 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).