From: Omar Sandoval <osandov@osandov.com>
To: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: kernel-team@fb.com
Subject: [PATCH] sched/wait: fix add_wait_queue() behavior change
Date: Tue, 5 Dec 2017 23:15:31 -0800 [thread overview]
Message-ID: <a16c8ccffd39bd08fdaa45a5192294c784b803a7.1512544324.git.osandov@fb.com> (raw)
In-Reply-To: <CA+55aFwhq-ZyDW2SYhYDg1ytKybwHywiH9jW3UmMu=YAgk694Q@mail.gmail.com>
From: Omar Sandoval <osandov@fb.com>
Commit 50816c48997a ("sched/wait: Standardize internal naming of
wait-queue entries") changed the behavior of add_wait_queue() from
inserting the wait entry at the head of the wait queue to the tail of
the wait queue. That commit was a cleanup and didn't mention any
functional changes so it was likely unintentional. This change in
behavior theoretically breaks wait queues which mix exclusive and
non-exclusive waiters, as non-exclusive waiters will not be woken up if
they are queued behind enough exclusive waiters.
Signed-off-by: Omar Sandoval <osandov@fb.com>
---
Since Ingo hasn't replied, here's a proper patch.
kernel/sched/wait.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/wait.c b/kernel/sched/wait.c
index 98feab7933c7..929ecb7d6b78 100644
--- a/kernel/sched/wait.c
+++ b/kernel/sched/wait.c
@@ -27,7 +27,7 @@ void add_wait_queue(struct wait_queue_head *wq_head, struct wait_queue_entry *wq
wq_entry->flags &= ~WQ_FLAG_EXCLUSIVE;
spin_lock_irqsave(&wq_head->lock, flags);
- __add_wait_queue_entry_tail(wq_head, wq_entry);
+ __add_wait_queue(wq_head, wq_entry);
spin_unlock_irqrestore(&wq_head->lock, flags);
}
EXPORT_SYMBOL(add_wait_queue);
--
2.15.1
next prev parent reply other threads:[~2017-12-06 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 0:58 add_wait_queue() (unintentional?) behavior change in v4.13 Omar Sandoval
2017-11-30 2:37 ` Linus Torvalds
2017-12-06 7:15 ` Omar Sandoval [this message]
2017-12-06 16:11 ` [PATCH] sched/wait: fix add_wait_queue() behavior change Jens Axboe
2017-12-06 16:46 ` Ingo Molnar
2017-12-06 20:28 ` [tip:sched/core] sched/wait: Fix add_wait_queue() behavioral change tip-bot for Omar Sandoval
2017-12-06 16:43 ` add_wait_queue() (unintentional?) behavior change in v4.13 Ingo Molnar
2017-12-06 2:35 ` Fubo Chen
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=a16c8ccffd39bd08fdaa45a5192294c784b803a7.1512544324.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).