From: akpm@linux-foundation.org
To: hch@lst.de, mingo@redhat.com, peterz@infradead.org,
viro@zeniv.linux.org.uk, mm-commits@vger.kernel.org
Subject: [obsolete] sched-wait-assert-the-wait_queue_head-lock-is-held-in-__wake_up_common.patch removed from -mm tree
Date: Wed, 13 Dec 2017 17:02:02 -0800 [thread overview]
Message-ID: <5a31cd8a.pdk8BtBPVBEc5+e0%akpm@linux-foundation.org> (raw)
The patch titled
Subject: sched/wait: assert the wait_queue_head lock is held in __wake_up_common
has been removed from the -mm tree. Its filename was
sched-wait-assert-the-wait_queue_head-lock-is-held-in-__wake_up_common.patch
This patch was dropped because it is obsolete
------------------------------------------------------
From: Christoph Hellwig <hch@lst.de>
Subject: sched/wait: assert the wait_queue_head lock is held in __wake_up_common
Better ensure we actually hold the lock using lockdep than just commenting
on it. Due to the various exported _locked interfaces it is far too easy
to get the locking wrong.
Link: http://lkml.kernel.org/r/20171130142037.19339-2-hch@lst.de
Signed-off-by: Christoph Hellwig <hch@lst.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/sched/wait.c | 2 ++
1 file changed, 2 insertions(+)
diff -puN kernel/sched/wait.c~sched-wait-assert-the-wait_queue_head-lock-is-held-in-__wake_up_common kernel/sched/wait.c
--- a/kernel/sched/wait.c~sched-wait-assert-the-wait_queue_head-lock-is-held-in-__wake_up_common
+++ a/kernel/sched/wait.c
@@ -76,6 +76,8 @@ static int __wake_up_common(struct wait_
wait_queue_entry_t *curr, *next;
int cnt = 0;
+ lockdep_assert_held(&wq_head->lock);
+
if (bookmark && (bookmark->flags & WQ_FLAG_BOOKMARK)) {
curr = list_next_entry(bookmark, entry);
_
Patches currently in -mm which might be from hch@lst.de are
reply other threads:[~2017-12-14 1:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5a31cd8a.pdk8BtBPVBEc5+e0%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mm-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.