From: tip-bot for Suresh Siddha <suresh.b.siddha@intel.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
suresh.b.siddha@intel.com, tglx@linutronix.de
Subject: [tip:x86/urgent] x86, compat: Use test_thread_flag(TIF_IA32) in compat signal delivery
Date: Fri, 15 Jun 2012 20:14:10 -0700 [thread overview]
Message-ID: <tip-0b91f45b23cb73ce11acdc3cf4c6efd4441e3b3e@git.kernel.org> (raw)
In-Reply-To: <1339722435.3475.57.camel@sbsiddha-desk.sc.intel.com>
Commit-ID: 0b91f45b23cb73ce11acdc3cf4c6efd4441e3b3e
Gitweb: http://git.kernel.org/tip/0b91f45b23cb73ce11acdc3cf4c6efd4441e3b3e
Author: Suresh Siddha <suresh.b.siddha@intel.com>
AuthorDate: Thu, 14 Jun 2012 18:07:15 -0700
Committer: H. Peter Anvin <hpa@zytor.com>
CommitDate: Thu, 14 Jun 2012 18:16:04 -0700
x86, compat: Use test_thread_flag(TIF_IA32) in compat signal delivery
Signal delivery compat path may not have the 'TS_COMPAT' flag (that
flag indicates how we entered the kernel). So use
test_thread_flag(TIF_IA32) instead of is_ia32_task(): one of the
functions of TIF_IA32 is just what kind of signal frame we want.
Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
Link: http://lkml.kernel.org/r/1339722435.3475.57.camel@sbsiddha-desk.sc.intel.com
Cc: stable@kernel.org # v3.4
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
arch/x86/ia32/ia32_signal.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/ia32/ia32_signal.c b/arch/x86/ia32/ia32_signal.c
index daeca56..673ac9b 100644
--- a/arch/x86/ia32/ia32_signal.c
+++ b/arch/x86/ia32/ia32_signal.c
@@ -38,7 +38,7 @@
int copy_siginfo_to_user32(compat_siginfo_t __user *to, siginfo_t *from)
{
int err = 0;
- bool ia32 = is_ia32_task();
+ bool ia32 = test_thread_flag(TIF_IA32);
if (!access_ok(VERIFY_WRITE, to, sizeof(compat_siginfo_t)))
return -EFAULT;
next prev parent reply other threads:[~2012-06-16 3:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 0:03 [RFC] x86, fpu: unify signal handling code paths for x86 and x86_64 kernels Suresh Siddha
2012-06-13 0:17 ` H. Peter Anvin
2012-06-14 14:37 ` Hans Rosenfeld
2012-06-14 20:45 ` Suresh Siddha
2012-06-15 0:10 ` Suresh Siddha
2012-06-15 0:16 ` H. Peter Anvin
2012-06-15 1:07 ` Suresh Siddha
2012-06-15 1:13 ` H. Peter Anvin
2012-06-15 1:16 ` Suresh Siddha
2012-06-15 1:17 ` H. Peter Anvin
2012-06-16 3:14 ` tip-bot for Suresh Siddha [this message]
2012-06-14 20:48 ` H. Peter Anvin
2012-06-14 20:49 ` Suresh Siddha
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=tip-0b91f45b23cb73ce11acdc3cf4c6efd4441e3b3e@git.kernel.org \
--to=suresh.b.siddha@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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