From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Jason Wang <jasowang@redhat.com>
Cc: rusty@rustcorp.com.au, mst@redhat.com,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] virito: introduce methods of fixing device features
Date: Thu, 13 Nov 2014 10:14:56 +0100 [thread overview]
Message-ID: <20141113101456.43acfdb7.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <546475C2.50606@redhat.com>
On Thu, 13 Nov 2014 17:11:30 +0800
Jason Wang <jasowang@redhat.com> wrote:
> On 11/13/2014 04:46 PM, Cornelia Huck wrote:
> > On Thu, 13 Nov 2014 13:52:53 +0800
> > Jason Wang <jasowang@redhat.com> wrote:
> >> +static inline void virtio_disable_feature(struct virtio_device *vdev,
> >> + unsigned int fbit)
> >> +{
> >> + BUG_ON(fbit >= VIRTIO_TRANSPORT_F_START);
> >> + BUG_ON(vdev->config->get_status(vdev) &
> >> + ~(VIRTIO_CONFIG_S_ACKNOWLEDGE | VIRTIO_CONFIG_S_DRIVER));
> > When we add virtio-1 support, we can add a check for FEATURES_OK here,
> > so we're really on the safe side.
> >
>
> If I read the spec correctly, FEATURES_OK was set only after writing the
> features bits to device. But we want to sanitize the them before.
I meant doing a BUG when FEATURES_OK is set - sorry for not being clear.
next prev parent reply other threads:[~2014-11-13 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 5:52 Jason Wang
2014-11-13 5:52 ` [PATCH 2/2] virtio-net: fix buggy features advertised by host Jason Wang
2014-11-13 6:06 ` Wanlong Gao
2014-11-13 6:45 ` Jason Wang
2014-11-13 8:53 ` Cornelia Huck
2014-11-13 9:12 ` Jason Wang
2014-11-13 8:46 ` [PATCH 1/2] virito: introduce methods of fixing device features Cornelia Huck
2014-11-13 9:11 ` Jason Wang
2014-11-13 9:14 ` Cornelia Huck [this message]
2014-11-13 9:49 ` Jason Wang
2014-11-24 1:08 ` Rusty Russell
2014-11-26 7:09 ` Jason Wang
-- strict thread matches above, loose matches on Subject: below --
2014-11-13 5:24 Jason Wang
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=20141113101456.43acfdb7.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome