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 12/13] xen/pvcalls: implement release command
Date: Fri, 22 Sep 2017 18:43:07 -0400 [thread overview]
Message-ID: <fe455763-4ced-0679-85ce-4f1d59c96f61@oracle.com> (raw)
In-Reply-To: <1505516440-11111-12-git-send-email-sstabellini@kernel.org>
>
> +static void pvcalls_front_free_map(struct pvcalls_bedata *bedata,
> + struct sock_mapping *map)
I just noticed: pvcalls_front_free_map() is referenced by patches 2 and 8.
> +{
> + int i;
> +
> + unbind_from_irqhandler(map->active.irq, map);
> +
> + spin_lock(&bedata->socket_lock);
> + if (!list_empty(&map->list))
> + list_del_init(&map->list);
> + spin_unlock(&bedata->socket_lock);
> +
> + for (i = 0; i < (1 << PVCALLS_RING_ORDER); i++)
> + gnttab_end_foreign_access(map->active.ring->ref[i], 0, 0);
> + gnttab_end_foreign_access(map->active.ref, 0, 0);
> + free_page((unsigned long)map->active.ring);
> +}
> +
> int pvcalls_front_socket(struct socket *sock)
> {
> struct pvcalls_bedata *bedata;
> @@ -960,6 +978,92 @@ unsigned int pvcalls_front_poll(struct file *file, struct socket *sock,
> return ret;
> }
>
> +int pvcalls_front_release(struct socket *sock)
> +{
> + struct pvcalls_bedata *bedata;
> + struct sock_mapping *map;
> + int req_id, notify, ret;
> + struct xen_pvcalls_request *req;
> +
> + pvcalls_enter;
> + if (!pvcalls_front_dev) {
> + pvcalls_exit;
> + return -EIO;
> + }
> + if (sock->sk == NULL) {
> + pvcalls_exit;
> + return 0;
> + }
> +
> + bedata = dev_get_drvdata(&pvcalls_front_dev->dev);
> +
> + map = (struct sock_mapping *) sock->sk->sk_send_head;
> + if (map == NULL) {
> + pvcalls_exit;
> + return 0;
> + }
> +
> + spin_lock(&bedata->socket_lock);
> + ret = get_request(bedata, &req_id);
> + if (ret < 0) {
> + spin_unlock(&bedata->socket_lock);
> + pvcalls_exit;
> + return ret;
> + }
> + sock->sk->sk_send_head = NULL;
> +
> + req = RING_GET_REQUEST(&bedata->ring, req_id);
> + req->req_id = req_id;
> + req->cmd = PVCALLS_RELEASE;
> + req->u.release.id = (uint64_t)map;
> +
> + bedata->ring.req_prod_pvt++;
> + RING_PUSH_REQUESTS_AND_CHECK_NOTIFY(&bedata->ring, notify);
> + spin_unlock(&bedata->socket_lock);
> + if (notify)
> + notify_remote_via_irq(bedata->irq);
> +
> + wait_event(bedata->inflight_req,
> + READ_ONCE(bedata->rsp[req_id].req_id) == req_id);
> +
> + if (map->active_socket) {
> + /*
> + * Set in_error and wake up inflight_conn_req to force
> + * recvmsg waiters to exit.
> + */
> + map->active.ring->in_error = -EBADF;
> + wake_up_interruptible(&map->active.inflight_conn_req);
> +
> + /*
> + * Wait until there are no more waiters on the mutexes.
> + * We know that no new waiters can be added because sk_send_head
> + * is set to NULL -- we only need to wait for the existing
> + * waiters to return.
> + */
> + while (!mutex_trylock(&map->active.in_mutex) ||
> + !mutex_trylock(&map->active.out_mutex))
> + cpu_relax();
What if you manage to grab the locks before waiters get to run? for
example, in recvmsg:
while (!(flags & MSG_DONTWAIT) && !pvcalls_front_read_todo(map)) {
wait_event_interruptible(map->active.inflight_conn_req,
pvcalls_front_read_todo(map));
}
ret = __read_ring(map->active.ring, &map->active.data,
&msg->msg_iter, len, flags);
map will be freed (by pvcalls_front_free_map() below) before __read_ring
is passed the just-freed ring.
> +
> + pvcalls_front_free_map(bedata, map);
> + kfree(map);
-boris
next prev parent reply other threads:[~2017-09-22 22:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 23:00 [PATCH v4 00/13] introduce the Xen PV Calls frontend Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 01/13] xen/pvcalls: introduce the pvcalls xenbus frontend Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 02/13] xen/pvcalls: implement frontend disconnect Stefano Stabellini
2017-09-20 20:32 ` Boris Ostrovsky
2017-10-06 17:51 ` Stefano Stabellini
2017-10-06 20:21 ` Boris Ostrovsky
2017-10-06 20:29 ` Stefano Stabellini
2017-10-06 20:31 ` Boris Ostrovsky
2017-09-20 20:59 ` Boris Ostrovsky
2017-10-07 0:08 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 03/13] xen/pvcalls: connect to the backend Stefano Stabellini
2017-09-20 21:08 ` Boris Ostrovsky
2017-09-15 23:00 ` [PATCH v4 04/13] xen/pvcalls: implement socket command and handle events Stefano Stabellini
2017-09-21 17:42 ` Boris Ostrovsky
2017-10-06 18:38 ` Stefano Stabellini
2017-10-06 20:36 ` Boris Ostrovsky
2017-09-15 23:00 ` [PATCH v4 05/13] xen/pvcalls: implement connect command Stefano Stabellini
2017-09-21 18:28 ` Boris Ostrovsky
2017-10-06 17:44 ` Stefano Stabellini
2017-10-06 17:54 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 06/13] xen/pvcalls: implement bind command Stefano Stabellini
2017-09-21 19:40 ` Boris Ostrovsky
2017-10-06 20:35 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 07/13] xen/pvcalls: implement listen command Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 08/13] xen/pvcalls: implement accept command Stefano Stabellini
2017-09-22 0:00 ` Boris Ostrovsky
2017-10-06 22:06 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 09/13] xen/pvcalls: implement sendmsg Stefano Stabellini
2017-09-22 21:57 ` Boris Ostrovsky
2017-10-06 21:43 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 10/13] xen/pvcalls: implement recvmsg Stefano Stabellini
2017-09-22 22:05 ` Boris Ostrovsky
2017-10-06 20:46 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 11/13] xen/pvcalls: implement poll command Stefano Stabellini
2017-09-19 15:19 ` Andrea Parri
2017-10-06 23:33 ` Stefano Stabellini
2017-09-22 22:27 ` Boris Ostrovsky
2017-10-06 23:39 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 12/13] xen/pvcalls: implement release command Stefano Stabellini
2017-09-22 22:43 ` Boris Ostrovsky [this message]
2017-09-22 22:48 ` Boris Ostrovsky
2017-10-06 23:49 ` Stefano Stabellini
2017-09-15 23:00 ` [PATCH v4 13/13] xen: introduce a Kconfig option to enable the pvcalls frontend 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=fe455763-4ced-0679-85ce-4f1d59c96f61@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®