From: bsegall@google.com
To: linux-kernel@vger.kernel.org,
Roland McGrath <roland@hack.frob.com>,
Oleg Nesterov <oleg@redhat.com>
Subject: [PATCH] ptrace: fix PTRACE_LISTEN race corrupting task->state
Date: Tue, 21 Feb 2017 10:47:54 -0800 [thread overview]
Message-ID: <xm2637f7js85.fsf@bsegall-linux.mtv.corp.google.com> (raw)
In PT_SEIZED + LISTEN mode SIGSTOP/SIGCONT signals cause a wakeup
against __TASK_TRACED. If this races with the ptrace_unfreeze_traced at
the end of a PTRACE_LISTEN, this can wake the task /after/ the check
against __TASK_TRACED, but before the reset of state to TASK_TRACED.
This causes it to instead clobber TASK_WAKING, allowing a subsequent
wakeup against TASK_TRACED while the task is still on the rq wake_list,
corrupting it.
Signed-off-by: Ben Segall <bsegall@google.com>
---
kernel/ptrace.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/kernel/ptrace.c b/kernel/ptrace.c
index 0af928712174..852d71440ded 100644
--- a/kernel/ptrace.c
+++ b/kernel/ptrace.c
@@ -184,10 +184,14 @@ static void ptrace_unfreeze_traced(struct task_struct *task)
WARN_ON(!task->ptrace || task->parent != current);
+ /*
+ * Double check __TASK_TRACED under the lock to prevent corrupting state
+ * in case of a ptrace_trap_notify wakeup
+ */
spin_lock_irq(&task->sighand->siglock);
if (__fatal_signal_pending(task))
wake_up_state(task, __TASK_TRACED);
- else
+ else if (task->state == __TASK_TRACED)
task->state = TASK_TRACED;
spin_unlock_irq(&task->sighand->siglock);
}
--
2.11.0.483.g087da7b7c-goog
next reply other threads:[~2017-02-21 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 18:47 bsegall [this message]
2017-02-22 16:55 ` Oleg Nesterov
2017-02-22 17:03 ` Oleg Nesterov
2017-02-22 17:56 ` bsegall
2017-02-24 16:36 ` Oleg Nesterov
2017-02-27 18:08 ` bsegall
2017-04-04 21:47 ` [PATCHv2] " bsegall
2017-04-04 21:53 ` Andrew Morton
2017-04-05 12:36 ` Oleg Nesterov
2017-04-05 12:30 ` Oleg Nesterov
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=xm2637f7js85.fsf@bsegall-linux.mtv.corp.google.com \
--to=bsegall@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=roland@hack.frob.com \
/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
Powered by JetHome