From: Peter Zijlstra <peterz@infradead.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: tatsu@ab.jp.nec.com, mingo@redhat.com,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: net: Generalise wq_has_sleeper helper
Date: Wed, 25 Nov 2015 10:15:33 +0100 [thread overview]
Message-ID: <20151125091533.GX17308@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20151124055423.GA31611@gondor.apana.org.au>
On Tue, Nov 24, 2015 at 01:54:23PM +0800, Herbert Xu wrote:
> diff --git a/include/linux/wait.h b/include/linux/wait.h
> index 1e1bf9f..bd1157f 100644
> --- a/include/linux/wait.h
> +++ b/include/linux/wait.h
> @@ -107,6 +107,50 @@ static inline int waitqueue_active(wait_queue_head_t *q)
> return !list_empty(&q->task_list);
> }
>
> +/**
> + * wq_has_sleeper - check if there are any waiting processes
> + * @wq: wait queue head
> + *
> + * Returns true if wq has waiting processes
> + *
> + * The purpose of the wq_has_sleeper and sock_poll_wait is to wrap the memory
> + * barrier call. They were added due to the race found within the tcp code.
> + *
> + * Consider following tcp code paths:
> + *
> + * CPU1 CPU2
> + *
> + * sys_select receive packet
> + * ... ...
> + * __add_wait_queue update tp->rcv_nxt
> + * ... ...
> + * tp->rcv_nxt check sock_def_readable
> + * ... {
> + * schedule rcu_read_lock();
> + * wq = rcu_dereference(sk->sk_wq);
> + * if (wq && waitqueue_active(&wq->wait))
> + * wake_up_interruptible(&wq->wait)
> + * ...
> + * }
> + *
> + * The race for tcp fires when the __add_wait_queue changes done by CPU1 stay
> + * in its cache, and so does the tp->rcv_nxt update on CPU2 side. The CPU1
> + * could then endup calling schedule and sleep forever if there are no more
> + * data on the socket.
> + *
Would be easier to refer to the comment that now adorns
waitqueue_active().
> + */
> +static inline bool wq_has_sleeper(wait_queue_head_t *wq)
> +{
> + /* We need to be sure we are in sync with the
broken comment style.
> + * add_wait_queue modifications to the wait queue.
> + *
> + * This memory barrier should be paired with one on the
> + * waiting side.
> + */
> + smp_mb();
> + return waitqueue_active(wq);
> +}
> +
> extern void add_wait_queue(wait_queue_head_t *q, wait_queue_t *wait);
> extern void add_wait_queue_exclusive(wait_queue_head_t *q, wait_queue_t *wait);
> extern void remove_wait_queue(wait_queue_head_t *q, wait_queue_t *wait);
next prev parent reply other threads:[~2015-11-25 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 8:01 [PATCH v2] wait: add comment before waitqueue_active noting memory barrier is required Kosuke Tatsukawa
2015-10-22 12:56 ` Peter Zijlstra
2015-10-22 23:18 ` Kosuke Tatsukawa
2015-10-23 12:40 ` Peter Zijlstra
2015-11-11 9:48 ` Herbert Xu
2015-11-24 5:54 ` net: Generalise wq_has_sleeper helper Herbert Xu
2015-11-24 21:30 ` David Miller
2015-11-25 1:10 ` Herbert Xu
2015-11-25 9:15 ` Peter Zijlstra [this message]
2015-11-25 16:37 ` David Miller
2015-11-26 5:55 ` [PATCH v2] " Herbert Xu
2015-11-30 19:46 ` David Miller
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=20151125091533.GX17308@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=tatsu@ab.jp.nec.com \
/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
Powered by JetHome