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 07/18] xen/pvcalls: implement socket command
Date: Mon, 15 May 2017 22:12:33 -0400 [thread overview]
Message-ID: <f183e016-01e3-6417-93c7-300e2aba7151@oracle.com> (raw)
In-Reply-To: <1494880570-14209-7-git-send-email-sstabellini@kernel.org>
On 05/15/2017 04:35 PM, Stefano Stabellini wrote:
> Just reply with success to the other end for now. Delay the allocation
> of the actual socket to bind and/or connect.
>
> Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
> CC: boris.ostrovsky@oracle.com
> CC: jgross@suse.com
> ---
> drivers/xen/pvcalls-back.c | 31 ++++++++++++++++++++++++++++++-
> 1 file changed, 30 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c
> index 2b2a49a..2eae096 100644
> --- a/drivers/xen/pvcalls-back.c
> +++ b/drivers/xen/pvcalls-back.c
> @@ -12,12 +12,17 @@
> * GNU General Public License for more details.
> */
>
> +#include <linux/inet.h>
> #include <linux/kthread.h>
> #include <linux/list.h>
> #include <linux/radix-tree.h>
> #include <linux/module.h>
> #include <linux/rwsem.h>
> #include <linux/wait.h>
> +#include <net/sock.h>
> +#include <net/inet_common.h>
> +#include <net/inet_connection_sock.h>
> +#include <net/request_sock.h>
>
> #include <xen/events.h>
> #include <xen/grant_table.h>
> @@ -65,7 +70,31 @@ static void pvcalls_back_ioworker(struct work_struct *work)
> static int pvcalls_back_socket(struct xenbus_device *dev,
> struct xen_pvcalls_request *req)
> {
> - return 0;
> + struct pvcalls_back_priv *priv;
> + int ret;
> + struct xen_pvcalls_response *rsp;
> +
> + if (dev == NULL)
> + return 0;
> + priv = dev_get_drvdata(&dev->dev);
This is inconsistent with pvcalls_back_event() tests, where you check
both for NULL. OTOH, I am not sure a check is needed at all since you've
just tested these in pvcalls_back_event().
-boris
> +
> + if (req->u.socket.domain != AF_INET ||
> + req->u.socket.type != SOCK_STREAM ||
> + (req->u.socket.protocol != 0 &&
> + req->u.socket.protocol != AF_INET))
> + ret = -EAFNOSUPPORT;
> + else
> + ret = 0;
> +
> + /* leave the actual socket allocation for later */
> +
> + rsp = RING_GET_RESPONSE(&priv->ring, priv->ring.rsp_prod_pvt++);
> + rsp->req_id = req->req_id;
> + rsp->cmd = req->cmd;
> + rsp->u.socket.id = req->u.socket.id;
> + rsp->ret = ret;
> +
> + return 1;
> }
>
> static int pvcalls_back_connect(struct xenbus_device *dev,
>
next prev parent reply other threads:[~2017-05-16 2:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 20:35 [PATCH 00/18] introduce the Xen PV Calls backend Stefano Stabellini
2017-05-15 20:35 ` [PATCH 01/18] xen: introduce the pvcalls interface header Stefano Stabellini
2017-05-15 20:35 ` [PATCH 02/18] xen/pvcalls: introduce the pvcalls xenbus backend Stefano Stabellini
2017-05-15 20:35 ` [PATCH 03/18] xen/pvcalls: initialize the module and register the " Stefano Stabellini
2017-05-16 1:28 ` Boris Ostrovsky
2017-05-16 20:05 ` Stefano Stabellini
2017-05-16 20:22 ` Stefano Stabellini
2017-05-16 6:40 ` Juergen Gross
2017-05-16 19:58 ` Stefano Stabellini
2017-05-17 5:21 ` Juergen Gross
2017-05-18 21:18 ` Stefano Stabellini
2017-05-19 22:33 ` Stefano Stabellini
2017-05-15 20:35 ` [PATCH 04/18] xen/pvcalls: xenbus state handling Stefano Stabellini
2017-05-16 1:34 ` Boris Ostrovsky
2017-05-16 20:11 ` Stefano Stabellini
2017-05-15 20:35 ` [PATCH 05/18] xen/pvcalls: connect to a frontend Stefano Stabellini
2017-05-16 1:52 ` Boris Ostrovsky
2017-05-16 20:23 ` Stefano Stabellini
2017-05-16 20:38 ` Stefano Stabellini
2017-05-15 20:35 ` [PATCH 06/18] xen/pvcalls: handle commands from the frontend Stefano Stabellini
2017-05-16 2:06 ` Boris Ostrovsky
2017-05-16 20:57 ` Stefano Stabellini
2017-05-15 20:35 ` [PATCH 07/18] xen/pvcalls: implement socket command Stefano Stabellini
2017-05-16 2:12 ` Boris Ostrovsky [this message]
2017-05-16 20:45 ` Stefano Stabellini
2017-05-15 20:36 ` [PATCH 08/18] xen/pvcalls: implement connect command Stefano Stabellini
2017-05-16 2:36 ` Boris Ostrovsky
2017-05-16 21:02 ` Stefano Stabellini
2017-05-16 21:56 ` Boris Ostrovsky
2017-05-18 19:10 ` Stefano Stabellini
2017-05-18 20:19 ` Boris Ostrovsky
2017-05-15 20:36 ` [PATCH 09/18] xen/pvcalls: implement bind command Stefano Stabellini
2017-05-15 20:36 ` [PATCH 10/18] xen/pvcalls: implement listen command Stefano Stabellini
2017-05-15 20:36 ` [PATCH 11/18] xen/pvcalls: implement accept command Stefano Stabellini
2017-05-15 20:36 ` [PATCH 12/18] xen/pvcalls: implement poll command Stefano Stabellini
2017-05-15 20:36 ` [PATCH 13/18] xen/pvcalls: implement release command Stefano Stabellini
2017-05-15 20:36 ` [PATCH 14/18] xen/pvcalls: disconnect and module_exit Stefano Stabellini
2017-05-15 20:36 ` [PATCH 15/18] xen/pvcalls: introduce the ioworker Stefano Stabellini
2017-05-15 20:36 ` [PATCH 16/18] xen/pvcalls: implement read Stefano Stabellini
2017-05-15 20:36 ` [PATCH 17/18] xen/pvcalls: implement write Stefano Stabellini
2017-05-15 20:36 ` [PATCH 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=f183e016-01e3-6417-93c7-300e2aba7151@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®