From: Lyu Mitnick <mitnick.lyu@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] Question about total_sectors in block/vpc.c
Date: Sun, 10 Apr 2011 17:02:20 +0800 [thread overview]
Message-ID: <BANLkTikLnE0g=9rkkLw3Pk+UPo5HSYxCUg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=-x2AgNnQ8t9H=kaAT45Az3m782w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]
Hello Stefan,
Is it your means:
There is an assumption that a block device cannot be addressed below 512
byte sectors.
A reasonable protection in block.c:bdrv_create() to check whether size is a
multiple of BDRV_SECTOR_SIZE.
Signed-off-by: Mitnick Lyu <mitnick.lyu@gmail.com>
---
block.c | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/block.c b/block.c
index f731c7a..a80ec49 100644
--- a/block.c
+++ b/block.c
@@ -239,6 +239,16 @@ int bdrv_create(BlockDriver *drv, const char* filename,
if (!drv->bdrv_create)
return -ENOTSUP;
+ while (options && options->name) {
+ if (!strcmp(options->name, "size")) {
+ if (options->value.n % 512 == 0)
+ break;
+ else
+ return -EINVAL;
+ }
+ options++;
+ }
+
return drv->bdrv_create(filename, options);
}
--
1.7.0.4
2011/4/10 Stefan Hajnoczi <stefanha@gmail.com>
> On Sat, Apr 9, 2011 at 5:51 PM, Lyu Mitnick <mitnick.lyu@gmail.com> wrote:
> > Hell all,
> > I have take a look of block/vpc.c and meet a question in vpc_create(). At
> > the line
> > 550, the code is:
> > total_sectors = options->value.n / 512;
> > I am wondering whether the size between total_sectors * 512
> > and options->value.n
> > would be discard.
>
> Yes, it rounds down. This reflects the assumption that a block device
> cannot be addressed below 512 byte sectors. Because of this block
> devices size must be a multiple of 512 bytes.
>
> I think a reasonable protection would be to have block.c:bdrv_create()
> fail if size is not a multiple of BDRV_SECTOR_SIZE. This way other
> image formats are protected too.
>
> Stefan
>
By the way, how could I know a submitted patch is accepted or not??
Thanks a lot
Mitnick
[-- Attachment #2: Type: text/html, Size: 2784 bytes --]
next prev parent reply other threads:[~2011-04-10 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 16:51 [Qemu-devel] Question about total_sectors in block/vpc.c Lyu Mitnick
2011-04-09 20:05 ` Stefan Hajnoczi
2011-04-10 9:02 ` Lyu Mitnick [this message]
2011-04-11 8:33 ` Stefan Hajnoczi
2011-04-13 20:59 ` Lyu Mitnick
2011-04-14 8:37 ` Kevin Wolf
2011-04-15 20:40 ` Lyu Mitnick
2011-04-18 13:13 ` Kevin Wolf
2011-04-11 18:14 ` Christoph Hellwig
2011-04-11 22:40 ` Lyu Mitnick
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='BANLkTikLnE0g=9rkkLw3Pk+UPo5HSYxCUg@mail.gmail.com' \
--to=mitnick.lyu@gmail.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--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).