From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xen.org, linux-kernel@vger.kernel.org,
jgross@suse.com, Stefano Stabellini <stefano@aporeto.com>
Subject: Re: [PATCH v4 12/18] xen/pvcalls: implement poll command
Date: Wed, 21 Jun 2017 16:55:56 -0400 [thread overview]
Message-ID: <599ef1d4-cdf0-8710-ea96-cda9cc47a7c6@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1706211331590.12819@sstabellini-ThinkPad-X260>
>>> +
>>> + mappass->reqcopy = *req;
>>> + icsk = inet_csk(mappass->sock->sk);
>>> + queue = &icsk->icsk_accept_queue;
>>> + spin_lock(&queue->rskq_lock);
>>> + data = queue->rskq_accept_head != NULL;
>>> + spin_unlock(&queue->rskq_lock);
>> What is the purpose of the queue lock here?
> It is only there to protect accesses to rskq_accept_head. Functions that
> change rskq_accept_head take this lock, see for example
> net/ipv4/inet_connection_sock.c:inet_csk_reqsk_queue_add. I'll add an
> in-code comment.
I am not sure I follow. You are not changing rskq_accept_head, you are
simply reading it under the lock. It may be set by others to NULL as
soon as you drop the lock, at which point 'data' test below will be
obsolete.
In inet_csk_reqsk_queue_add() it is read and then, based on read result,
is written with a value so a lock is indeed need there.
-boris
>
>
>>> + if (data) {
>>> + mappass->reqcopy.cmd = 0;
>>> + ret = 0;
>>> + goto out;
>>> + }
>>> + spin_unlock_irqrestore(&mappass->copy_lock, flags);
>>> +
>>> + /* Tell the caller we don't need to send back a notification yet */
>>> + return -1;
next prev parent reply other threads:[~2017-06-21 20:55 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
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 [this message]
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=599ef1d4-cdf0-8710-ea96-cda9cc47a7c6@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®