From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V6 0/3] handle polling errors in vhost/vhost_net
Date: Thu, 24 Jan 2013 12:38:07 +0200 [thread overview]
Message-ID: <20130124103807.GB9368@redhat.com> (raw)
In-Reply-To: <1358351078-58915-1-git-send-email-jasowang@redhat.com>
On Wed, Jan 16, 2013 at 11:44:35PM +0800, Jason Wang wrote:
> This is an update version of last version to fix the handling of polling errors
> in vhost/vhost_net.
>
> Currently, vhost and vhost_net ignore polling errors which can lead kernel
> crashing when it tries to remove itself from waitqueue after the polling
> failure. Fix this by:
>
> - examing the POLLERR when setting backend and report erros to userspace
> - let tun always add to waitqueue in .poll() after the queue is created even if
> it was detached.
>
> Changes from V5:
> - use rcu_dereference() instead of the wrong rtnl_dereference() in data path
> - test with CONFIG_PROVE_RCU
>
> Changes from V4:
> - check the detached state by tfile->detached and protect it by RCU
>
> Changes from V3:
> - make a smaller patch that doesn't touch the whole polling state and only check
> the polliner errors in backend setting.
> - add a patch that allows tuntap to do polling/reading/writing when detached
> which could simplify the work of its user.
>
> Changes from v2:
> - check poll->wqh instead of the wrong assumption about POLLERR and waitqueue
> - drop the whole tx polling state check since it was replaced by the wqh
> checking
> - drop the buggy tuntap patch
>
> Changes from v1:
> - restore the state before the ioctl when vhost_init_used() fails
> - log the error when meet polling errors in the data path
> - don't put into waitqueue when tun_chr_poll() return POLLERR
>
> Jason Wang (3):
> vhost_net: correct error handling in vhost_net_set_backend()
> vhost_net: handle polling errors when setting backend
> tuntap: allow polling/writing/reading when detached
>
> drivers/net/tun.c | 45 ++++++++++++++++++++++++++-------------------
> drivers/vhost/net.c | 41 ++++++++++++++++++++++++++++-------------
> drivers/vhost/vhost.c | 18 +++++++++++++++---
> drivers/vhost/vhost.h | 2 +-
> 4 files changed, 70 insertions(+), 36 deletions(-)
Acked-by: Michael S. Tsirkin <mst@redhat.com>
prev parent reply other threads:[~2013-01-24 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 15:44 [PATCH V6 0/3] handle polling errors in vhost/vhost_net Jason Wang
2013-01-16 15:44 ` [PATCH V6 1/3] vhost_net: correct error handling in vhost_net_set_backend() Jason Wang
2013-01-24 10:38 ` Michael S. Tsirkin
2013-01-16 15:44 ` [PATCH V6 2/3] vhost_net: handle polling errors when setting backend Jason Wang
2013-01-24 10:38 ` Michael S. Tsirkin
2013-01-16 15:44 ` [PATCH V6 3/3] tuntap: allow polling/writing/reading when detached Jason Wang
2013-01-16 17:03 ` Michael S. Tsirkin
2013-01-17 1:16 ` Jason Wang
2013-01-24 10:12 ` Jason Wang
2013-01-24 10:37 ` Michael S. Tsirkin
2013-01-24 10:38 ` Michael S. Tsirkin
2013-01-24 10:38 ` Michael S. Tsirkin [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=20130124103807.GB9368@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).