The patch titled
sigwait eats blocked default-ignore signals
has been removed from the -mm tree. Its filename was
sigwait-eats-blocked-default-ignore-signals.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: sigwait eats blocked default-ignore signals
From: Roland McGrath <roland@xxxxxxxxxx>
cf http://bugzilla.kernel.org/show_bug.cgi?id=9347
While a signal is blocked, it must be posted even if its action is SIG_IGN
or is SIG_DFL with the default action to ignore. This works right most of
the time, but is broken when a sigwait (rt_sigtimedwait) is in progress.
This changes the early-discard check to respect real_blocked. ~blocked is
the set to check for "should wake up now", but ~(blocked|real_blocked) is
the set for "blocked" semantics as defined by POSIX.
Signed-off-by: Roland McGrath <roland@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/signal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN kernel/signal.c~sigwait-eats-blocked-default-ignore-signals kernel/signal.c
--- a/kernel/signal.c~sigwait-eats-blocked-default-ignore-signals
+++ a/kernel/signal.c
@@ -55,7 +55,7 @@ static int sig_ignored(struct task_struc
* signal handler may change by the time it is
* unblocked.
*/
- if (sigismember(&t->blocked, sig))
+ if (sigismember(&t->blocked, sig) || sigismember(&t->real_blocked, sig))
return 0;
/* Is it explicitly or implicitly ignored? */
_
Patches currently in -mm which might be from roland@xxxxxxxxxx are
origin.patch
get_task_comm-return-the-result.patch
clone-prepare-to-recycle-clone_detached-and-clone_stopped.patch
i386-and-x86_64-randomize-brk.patch
i386-and-x86_64-randomize-brk-fix.patch
i386-and-x86_64-randomize-brk-fix-2.patch
pie-executable-randomization.patch
pie-executable-randomization-uninlining.patch
pie-executable-randomization-checkpatch-fixes.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
