From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio-blk: allow toggling host cache between writeback and writethrough
Date: Thu, 05 Jul 2012 08:45:56 +0200 [thread overview]
Message-ID: <4FF53824.6090303@redhat.com> (raw)
In-Reply-To: <20120704213037.GA27713@redhat.com>
Il 04/07/2012 23:30, Michael S. Tsirkin ha scritto:
>>>>>> +static int virtblk_get_cache_mode(struct virtio_device *vdev)
>>>>>
>>>>> Why are you converting u8 to int here?
>>>>
>>>> The fact that it is a u8 is really an internal detail. Perhaps the bug
>>>> is using u8 in the callers.
>>>
>>> Make it bool then?
>>>
>>> You are using u8 in the config. So you could get any value
>>> besides 0 and 1, and you interpret that as 1.
>>> Is 1 always a safe value? If not maybe it's better to set
>>> to a safe value if it is not 0 or 1, that is we don't know how to interpret it.
>>
>> That would be a host bug; the spec only gives meaning to 0 and 1.
>
> Yes but if the other side does not validate values implementations
> *will* have bugs. Why not declare bits 1-7 reserved?
Ok, that would be a different change. I thought about it yesterday, but
it seemed like a useless complication. It's not like we have been
adding configuration fields every other week. :)
But I can certainly prepare patches to both virtio-blk and the spec for
that if you prefer.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org, rusty@rustcorp.com.au,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio-blk: allow toggling host cache between writeback and writethrough
Date: Thu, 05 Jul 2012 08:45:56 +0200 [thread overview]
Message-ID: <4FF53824.6090303@redhat.com> (raw)
In-Reply-To: <20120704213037.GA27713@redhat.com>
Il 04/07/2012 23:30, Michael S. Tsirkin ha scritto:
>>>>>> +static int virtblk_get_cache_mode(struct virtio_device *vdev)
>>>>>
>>>>> Why are you converting u8 to int here?
>>>>
>>>> The fact that it is a u8 is really an internal detail. Perhaps the bug
>>>> is using u8 in the callers.
>>>
>>> Make it bool then?
>>>
>>> You are using u8 in the config. So you could get any value
>>> besides 0 and 1, and you interpret that as 1.
>>> Is 1 always a safe value? If not maybe it's better to set
>>> to a safe value if it is not 0 or 1, that is we don't know how to interpret it.
>>
>> That would be a host bug; the spec only gives meaning to 0 and 1.
>
> Yes but if the other side does not validate values implementations
> *will* have bugs. Why not declare bits 1-7 reserved?
Ok, that would be a different change. I thought about it yesterday, but
it seemed like a useless complication. It's not like we have been
adding configuration fields every other week. :)
But I can certainly prepare patches to both virtio-blk and the spec for
that if you prefer.
Paolo
next prev parent reply other threads:[~2012-07-05 6:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 13:19 [PATCH] virtio-blk: allow toggling host cache between writeback and writethrough Paolo Bonzini
2012-07-04 5:55 ` Rusty Russell
2012-07-04 6:24 ` Rusty Russell
2012-07-04 15:13 ` Michael S. Tsirkin
2012-07-04 15:42 ` Michael S. Tsirkin
2012-07-04 15:42 ` Michael S. Tsirkin
2012-07-04 15:54 ` Paolo Bonzini
2012-07-04 16:02 ` Michael S. Tsirkin
2012-07-04 16:02 ` Michael S. Tsirkin
2012-07-04 16:08 ` Paolo Bonzini
2012-07-04 16:08 ` Paolo Bonzini
2012-07-04 21:30 ` Michael S. Tsirkin
2012-07-04 21:30 ` Michael S. Tsirkin
2012-07-05 6:45 ` Paolo Bonzini [this message]
2012-07-05 6:45 ` Paolo Bonzini
2012-07-04 15:54 ` Paolo Bonzini
2012-07-04 16:26 ` Sasha Levin
2012-07-04 16:32 ` Paolo Bonzini
2012-07-04 21:11 ` Sasha Levin
2012-07-05 6:47 ` Paolo Bonzini
2012-07-05 7:02 ` Sasha Levin
2012-07-08 23:45 ` Rusty Russell
2012-07-25 1:02 ` Rusty Russell
2012-07-05 18:39 ` Badari Pulavarty
2012-07-06 6:47 ` Paolo Bonzini
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=4FF53824.6090303@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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.