From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Stefano Stabellini <sstabellini@kernel.org>, xen-devel@lists.xen.org
Cc: linux-kernel@vger.kernel.org, jgross@suse.com,
Stefano Stabellini <stefano@aporeto.com>
Subject: Re: [PATCH v4 11/18] xen/pvcalls: implement accept command
Date: Tue, 20 Jun 2017 12:02:15 -0400 [thread overview]
Message-ID: <fcbdad67-30ed-0049-de78-d501347fb561@oracle.com> (raw)
In-Reply-To: <1497553787-3709-11-git-send-email-sstabellini@kernel.org>
> static void __pvcalls_back_accept(struct work_struct *work)
> {
> + struct sockpass_mapping *mappass = container_of(
> + work, struct sockpass_mapping, register_work);
> + struct sock_mapping *map;
> + struct pvcalls_ioworker *iow;
> + struct pvcalls_fedata *fedata;
> + struct socket *sock;
> + struct xen_pvcalls_response *rsp;
> + struct xen_pvcalls_request *req;
> + int notify;
> + int ret = -EINVAL;
> + unsigned long flags;
> +
> + fedata = mappass->fedata;
> + /*
> + * __pvcalls_back_accept can race against pvcalls_back_accept.
> + * We only need to check the value of "cmd" on read. It could be
> + * done atomically, but to simplify the code on the write side, we
> + * use a spinlock.
> + */
> + spin_lock_irqsave(&mappass->copy_lock, flags);
> + req = &mappass->reqcopy;
> + if (req->cmd != PVCALLS_ACCEPT) {
> + spin_unlock_irqrestore(&mappass->copy_lock, flags);
> + return;
> + }
> + spin_unlock_irqrestore(&mappass->copy_lock, flags);
> +
> + sock = sock_alloc();
> + if (sock == NULL)
> + goto out_error;
> + sock->type = mappass->sock->type;
> + sock->ops = mappass->sock->ops;
> +
> + ret = inet_accept(mappass->sock, sock, O_NONBLOCK, true);
> + if (ret == -EAGAIN) {
> + sock_release(sock);
> + goto out_error;
> + }
> +
> + map = pvcalls_new_active_socket(fedata,
> + req->u.accept.id_new,
> + req->u.accept.ref,
> + req->u.accept.evtchn,
> + sock);
> + if (!map) {
> + sock_release(sock);
> + goto out_error;
Again, lost ret value.
> + }
> +
> + map->sockpass = mappass;
> + iow = &map->ioworker;
> + atomic_inc(&map->read);
> + atomic_inc(&map->io);
> + queue_work(iow->wq, &iow->register_work);
> +
> +out_error:
> + rsp = RING_GET_RESPONSE(&fedata->ring, fedata->ring.rsp_prod_pvt++);
> + rsp->req_id = req->req_id;
> + rsp->cmd = req->cmd;
> + rsp->u.accept.id = req->u.accept.id;
> + rsp->ret = ret;
> + RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(&fedata->ring, notify);
> + if (notify)
> + notify_remote_via_irq(fedata->irq);
> +
> + mappass->reqcopy.cmd = 0;
> }
>
> static void pvcalls_pass_sk_data_ready(struct sock *sock)
> {
> + struct sockpass_mapping *mappass = sock->sk_user_data;
> +
> + if (mappass == NULL)
> + return;
> +
> + queue_work(mappass->wq, &mappass->register_work);
> }
>
> static int pvcalls_back_bind(struct xenbus_device *dev,
> @@ -383,6 +456,43 @@ static int pvcalls_back_listen(struct xenbus_device *dev,
> static int pvcalls_back_accept(struct xenbus_device *dev,
> struct xen_pvcalls_request *req)
> {
> + struct pvcalls_fedata *fedata;
> + struct sockpass_mapping *mappass;
> + int ret = -EINVAL;
Unnecessary initialization.
-boris
> + struct xen_pvcalls_response *rsp;
> + unsigned long flags;
> +
> + fedata = dev_get_drvdata(&dev->dev);
> +
> + mappass = radix_tree_lookup(&fedata->socketpass_mappings,
> + req->u.accept.id);
> + if (mappass == NULL)
> + goto out_error;
> +
> + /*
> + * Limitation of the current implementation: only support one
> + * concurrent accept or poll call on one socket.
> + */
> + spin_lock_irqsave(&mappass->copy_lock, flags);
> + if (mappass->reqcopy.cmd != 0) {
> + spin_unlock_irqrestore(&mappass->copy_lock, flags);
> + ret = -EINTR;
> + goto out_error;
> + }
> +
> + mappass->reqcopy = *req;
> + spin_unlock_irqrestore(&mappass->copy_lock, flags);
> + queue_work(mappass->wq, &mappass->register_work);
> +
> + /* Tell the caller we don't need to send back a notification yet */
> + return -1;
> +
> +out_error:
> + rsp = RING_GET_RESPONSE(&fedata->ring, fedata->ring.rsp_prod_pvt++);
> + rsp->req_id = req->req_id;
> + rsp->cmd = req->cmd;
> + rsp->u.accept.id = req->u.accept.id;
> + rsp->ret = ret;
> return 0;
> }
>
next prev parent reply other threads:[~2017-06-20 16:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 19:09 [PATCH v4 00/18] introduce the Xen PV Calls backend Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 01/18] xen: introduce the pvcalls interface header Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 02/18] xen/pvcalls: introduce the pvcalls xenbus backend Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 03/18] xen/pvcalls: initialize the module and register the " Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 04/18] xen/pvcalls: xenbus state handling Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 05/18] xen/pvcalls: connect to a frontend Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 06/18] xen/pvcalls: handle commands from the frontend Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 07/18] xen/pvcalls: implement socket command Stefano Stabellini
2017-06-20 15:49 ` Boris Ostrovsky
2017-06-20 16:11 ` [Xen-devel] " Roger Pau Monné
2017-06-21 20:16 ` Stefano Stabellini
2017-06-22 8:26 ` Roger Pau Monné
2017-06-22 18:29 ` Stefano Stabellini
2017-06-22 18:36 ` Andrew Cooper
2017-06-22 18:38 ` Stefano Stabellini
2017-06-23 9:39 ` Roger Pau Monné
2017-06-15 19:09 ` [PATCH v4 08/18] xen/pvcalls: implement connect command Stefano Stabellini
2017-06-20 15:43 ` Boris Ostrovsky
2017-06-20 15:47 ` Boris Ostrovsky
2017-06-21 20:26 ` Stefano Stabellini
2017-06-21 20:25 ` Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 09/18] xen/pvcalls: implement bind command Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 10/18] xen/pvcalls: implement listen command Stefano Stabellini
2017-06-20 15:51 ` Boris Ostrovsky
2017-06-15 19:09 ` [PATCH v4 11/18] xen/pvcalls: implement accept command Stefano Stabellini
2017-06-20 16:02 ` Boris Ostrovsky [this message]
2017-06-21 20:29 ` Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 12/18] xen/pvcalls: implement poll command Stefano Stabellini
2017-06-20 16:43 ` Boris Ostrovsky
2017-06-21 20:39 ` Stefano Stabellini
2017-06-21 20:55 ` Boris Ostrovsky
2017-06-21 21:49 ` Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 13/18] xen/pvcalls: implement release command Stefano Stabellini
2017-06-20 17:15 ` Boris Ostrovsky
2017-06-21 21:33 ` Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 14/18] xen/pvcalls: disconnect and module_exit Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 15/18] xen/pvcalls: implement the ioworker functions Stefano Stabellini
2017-06-20 17:26 ` Boris Ostrovsky
2017-06-15 19:09 ` [PATCH v4 16/18] xen/pvcalls: implement read Stefano Stabellini
2017-06-21 22:37 ` Boris Ostrovsky
2017-06-21 23:32 ` Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 17/18] xen/pvcalls: implement write Stefano Stabellini
2017-06-15 19:09 ` [PATCH v4 18/18] xen: introduce a Kconfig option to enable the pvcalls backend Stefano Stabellini
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=fcbdad67-30ed-0049-de78-d501347fb561@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=stefano@aporeto.com \
--cc=xen-devel@lists.xen.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®