From: Bart Van Assche <bvanassche@acm.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>, Neil Brown <neilb@suse.de>,
Michael Shaver <jmshaver@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] sched: Avoid that __wait_on_bit_lock() hangs
Date: Sat, 6 Aug 2016 14:36:10 -0700 [thread overview]
Message-ID: <e6b146d9-bb6b-c4cc-9408-0fc77a612d1d@acm.org> (raw)
In-Reply-To: <6e70b9d5-05ea-72f7-b6fe-2c900a5b4266@sandisk.com>
On 08/05/16 16:09, Bart Van Assche wrote:
> If delivery of a signal and __wake_up_common() happen concurrently
> it is possible that the signal is delivered after __wake_up_common()
> woke up the affected task and before bit_wait_io() checks whether a
> signal is pending. Avoid that the next waiter is not woken up if this
> happens.
(replying to my own e-mail)
Although this patch works reliably in my tests, the above description
does not explain the hang. I will resend this patch with a better
description.
Bart.
next prev parent reply other threads:[~2016-08-06 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 23:08 [PATCH v2 0/3] " Bart Van Assche
2016-08-05 23:09 ` [PATCH v2 1/3] " Bart Van Assche
2016-08-06 21:36 ` Bart Van Assche [this message]
2016-08-09 17:24 ` Oleg Nesterov
2016-08-05 23:09 ` [PATCH v2 2/3] sched: Introduce a local variable in abort_exclusive_wait() Bart Van Assche
2016-08-05 23:10 ` [PATCH v2 3/3] sched: Avoid that abort_exclusive_wait() triggers spurious wakeups Bart Van Assche
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=e6b146d9-bb6b-c4cc-9408-0fc77a612d1d@acm.org \
--to=bvanassche@acm.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jmshaver@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=neilb@suse.de \
--cc=oleg@redhat.com \
--cc=peterz@infradead.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®