Subject: [merged] ptrace-task_clear_jobctl_trapping-wake_up_bit-needs-mb.patch removed from -mm tree
To: oleg@xxxxxxxxxx,peterz@xxxxxxxxxxxxx,mm-commits@xxxxxxxxxxxxxxx
From: akpm@xxxxxxxxxxxxxxxxxxxx
Date: Mon, 09 Jun 2014 12:33:32 -0700
The patch titled
Subject: ptrace: task_clear_jobctl_trapping()->wake_up_bit() needs mb()
has been removed from the -mm tree. Its filename was
ptrace-task_clear_jobctl_trapping-wake_up_bit-needs-mb.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Oleg Nesterov <oleg@xxxxxxxxxx>
Subject: ptrace: task_clear_jobctl_trapping()->wake_up_bit() needs mb()
__wake_up_bit() checks waitqueue_active() and thus the caller needs mb()
as wake_up_bit() documents, fix task_clear_jobctl_trapping().
Signed-off-by: Oleg Nesterov <oleg@xxxxxxxxxx>
Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/signal.c | 1 +
1 file changed, 1 insertion(+)
diff -puN kernel/signal.c~ptrace-task_clear_jobctl_trapping-wake_up_bit-needs-mb kernel/signal.c
--- a/kernel/signal.c~ptrace-task_clear_jobctl_trapping-wake_up_bit-needs-mb
+++ a/kernel/signal.c
@@ -277,6 +277,7 @@ void task_clear_jobctl_trapping(struct t
{
if (unlikely(task->jobctl & JOBCTL_TRAPPING)) {
task->jobctl &= ~JOBCTL_TRAPPING;
+ smp_mb(); /* advised by wake_up_bit() */
wake_up_bit(&task->jobctl, JOBCTL_TRAPPING_BIT);
}
}
_
Patches currently in -mm which might be from oleg@xxxxxxxxxx are
origin.patch
cpu-hotplug-smp-flush-any-pending-ipi-callbacks-before-cpu-offline.patch
linux-next.patch
kernel-watchdogc-print-traces-for-all-cpus-on-lockup-detection.patch
kernel-watchdogc-print-traces-for-all-cpus-on-lockup-detection-fix.patch
nmi-provide-the-option-to-issue-an-nmi-back-trace-to-every-cpu-but-current.patch
nmi-provide-the-option-to-issue-an-nmi-back-trace-to-every-cpu-but-current-fix.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
