From: David Miller <davem@davemloft.net>
To: mst@redhat.com
Cc: stefanha@redhat.com, virtualization@lists.linux-foundation.org,
torvalds@linux-foundation.org, jasowang@redhat.com,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] vhost: fix vhost_vq_access_ok() log check
Date: Wed, 11 Apr 2018 10:55:28 -0400 (EDT) [thread overview]
Message-ID: <20180411.105528.2200336972660597076.davem@davemloft.net> (raw)
In-Reply-To: <20180411162345-mutt-send-email-mst@kernel.org>
From: "Michael S. Tsirkin" <mst@redhat.com>
Date: Wed, 11 Apr 2018 16:24:02 +0300
> On Wed, Apr 11, 2018 at 10:35:39AM +0800, Stefan Hajnoczi wrote:
>> v3:
>> * Rebased onto net/master and resolved conflict [DaveM]
>>
>> v2:
>> * Rewrote the conditional to make the vq access check clearer [Linus]
>> * Added Patch 2 to make the return type consistent and harder to misuse [Linus]
>>
>> The first patch fixes the vhost virtqueue access check which was recently
>> broken. The second patch replaces the int return type with bool to prevent
>> future bugs.
>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
> We need the 1st one on stable I think.
Series applied and patch #1 queued up for -stable.
prev parent reply other threads:[~2018-04-11 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 2:35 Stefan Hajnoczi
2018-04-11 2:35 ` [PATCH v3 1/2] " Stefan Hajnoczi
2018-04-11 13:23 ` Michael S. Tsirkin
2018-04-11 2:35 ` [PATCH v3 2/2] vhost: return bool from *_access_ok() functions Stefan Hajnoczi
2018-04-11 13:23 ` Michael S. Tsirkin
2018-04-11 3:33 ` [PATCH v3 0/2] vhost: fix vhost_vq_access_ok() log check Jason Wang
2018-04-11 13:24 ` Michael S. Tsirkin
2018-04-11 14:55 ` David Miller [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=20180411.105528.2200336972660597076.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--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®