From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Sudeep Dutt <sudeep.dutt@intel.com>
Cc: gregkh@linuxfoundation.org, arnd@arndb.de,
ashutosh.dixit@intel.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, tiwei.bie@intel.com,
luto@kernel.org
Subject: Re: [PATCH] mic: vop: Fix broken virtqueues
Date: Wed, 30 Jan 2019 17:27:23 +0100 [thread overview]
Message-ID: <20190130162722.bnr5wlsbg767lslz@axis.com> (raw)
In-Reply-To: <1548865797.29684.47.camel@intel.com>
On Wed, Jan 30, 2019 at 08:29:57AM -0800, Sudeep Dutt wrote:
> On Tue, 2019-01-29 at 11:22 +0100, Vincent Whitchurch wrote:
> > VOP is broken in mainline since commit 1ce9e6055fa0a9043 ("virtio_ring:
> > introduce packed ring support"); attempting to use the virtqueues leads
> > to various kernel crashes. I'm testing it with my not-yet-merged
> > loopback patches, but even the in-tree MIC hardware cannot work.
> >
> > The problem is not in the referenced commit per se, but is due to the
> > following hack in vop_find_vq() which depends on the layout of private
> > structures in other source files, which that commit happened to change:
> >
> > /*
> > * To reassign the used ring here we are directly accessing
> > * struct vring_virtqueue which is a private data structure
> > * in virtio_ring.c. At the minimum, a BUILD_BUG_ON() in
> > * vring_new_virtqueue() would ensure that
> > * (&vq->vring == (struct vring *) (&vq->vq + 1));
> > */
> > vr = (struct vring *)(vq + 1);
> > vr->used = used;
> >
> > Fix vop by using __vring_new_virtqueue() to create the needed vring
> > layout from the start, instead of attempting to patch in the used ring
> > later. __vring_new_virtqueue() was added way back in commit
> > 2a2d1382fe9dcc ("virtio: Add improved queue allocation API") in order to
> > address mic's usecase, according to the commit message.
> >
>
> Thank you for fixing this up Vincent.
>
> Reviewed-by: Sudeep Dutt <sudeep.dutt@intel.com>
Thanks, but I just noticed that the removal patch has the hack too
(without a comment), so that needs to be fixed. I'll post a v2.
(The removal path also has an unrelated use-after-free, but that's a
subject for a different patch.)
prev parent reply other threads:[~2019-01-30 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 10:22 Vincent Whitchurch
2019-01-30 16:29 ` Sudeep Dutt
2019-01-30 16:27 ` Vincent Whitchurch [this message]
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=20190130162722.bnr5wlsbg767lslz@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=sudeep.dutt@intel.com \
--cc=tiwei.bie@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®