linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Neuling <mikey@neuling.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: powerpc: fix swapcontext backwards compatibility due to VSX ucontext changes
Date: Sun, 06 Jul 2008 18:37:16 +1000	[thread overview]
Message-ID: <28458.1215333436@neuling.org> (raw)
In-Reply-To: <18542.1169.106972.172938@cargo.ozlabs.ibm.com>

When the ucontext changed to add the VSX context, this broke backwards
compatibly on swapcontext.  swapcontext only compares the ucontext
size passed in from the user to the new kernel ucontext size.

This adds a check against the old ucontext size (with VMX but without
VSX).  It also adds some sanity check for ucontexts without VSX, but
where VSX is used according the MSR.  Fixes for both 32 and 64bit
processes on 64bit kernels

Kudos to Paulus for noticing.

Signed-off-by: Michael Neuling <mikey@neuling.org>
---
> > +	    /*
> > +	     * If userspace doesn't provide enough room for VSX data,
> > +	     * but current thread has used VSX, we don't have anywhere
> > +	     * to store the full context back into.
> > +	     */
> > +		((ctx_size < sizeof(struct ucontext)) &&
> > +		 (regs->msr & MSR_VSX) && old_ctx) ||
> 
> I think we need to check current->thread.used_vsr rather than
> regs->msr here (in both instances of this code).

Yep I agree.  Thanks

 arch/powerpc/kernel/signal_32.c |   36 +++++++++++++++++++++++++++++++++++-
 arch/powerpc/kernel/signal_64.c |   35 +++++++++++++++++++++++++++++++----
 2 files changed, 66 insertions(+), 5 deletions(-)

Index: linux-2.6-ozlabs/arch/powerpc/kernel/signal_32.c
===================================================================
--- linux-2.6-ozlabs.orig/arch/powerpc/kernel/signal_32.c
+++ linux-2.6-ozlabs/arch/powerpc/kernel/signal_32.c
@@ -68,6 +68,13 @@
 #define ucontext	ucontext32
 
 /*
+ * Userspace code may pass a ucontext which doesn't include VSX added
+ * at the end.  We need to check for this case.
+ */
+#define UCONTEXTSIZEWITHOUTVSX \
+		(sizeof(struct ucontext) - sizeof(elf_vsrreghalf_t32))
+
+/*
  * Returning 0 means we return to userspace via
  * ret_from_except and thus restore all user
  * registers from *regs.  This is what we need
@@ -930,12 +937,39 @@ long sys_swapcontext(struct ucontext __u
 {
 	unsigned char tmp;
 
+#ifdef CONFIG_PPC64
+	unsigned long new_msr = 0;
+
+	if (new_ctx &&
+	    __get_user(new_msr, &new_ctx->uc_mcontext.mc_gregs[PT_MSR]))
+		return -EFAULT;
+	if (/*
+	     * Check that the context is not smaller than the original
+	     * size (with VMX but without VSX)
+	     */
+		(ctx_size < UCONTEXTSIZEWITHOUTVSX) ||
+	    /*
+	     * If userspace doesn't provide enough room for VSX data,
+	     * but current thread has used VSX, we don't have anywhere
+	     * to store the full context back into.
+	     */
+		((ctx_size < sizeof(struct ucontext)) &&
+		 current->thread.used_vsr && old_ctx) ||
+	    /*
+	     * If the new context state sets the MSR VSX bits but
+	     * it doesn't provide VSX state.
+	     */
+		((ctx_size < sizeof(struct ucontext)) &&
+		 (new_msr & MSR_VSX)))
+		/* ... computer says "noooo" */
+		return -EINVAL;
+#else
 	/* Context size is for future use. Right now, we only make sure
 	 * we are passed something we understand
 	 */
 	if (ctx_size < sizeof(struct ucontext))
 		return -EINVAL;
-
+#endif
 	if (old_ctx != NULL) {
 		struct mcontext __user *mctx;
 
Index: linux-2.6-ozlabs/arch/powerpc/kernel/signal_64.c
===================================================================
--- linux-2.6-ozlabs.orig/arch/powerpc/kernel/signal_64.c
+++ linux-2.6-ozlabs/arch/powerpc/kernel/signal_64.c
@@ -268,6 +268,13 @@ static long setup_trampoline(unsigned in
 }
 
 /*
+ * Userspace code may pass a ucontext which doesn't include VSX added
+ * at the end.  We need to check for this case.
+ */
+#define UCONTEXTSIZEWITHOUTVSX \
+		(sizeof(struct ucontext) - 32*sizeof(long))
+
+/*
  * Handle {get,set,swap}_context operations
  */
 int sys_swapcontext(struct ucontext __user *old_ctx,
@@ -277,10 +284,30 @@ int sys_swapcontext(struct ucontext __us
 	unsigned char tmp;
 	sigset_t set;
 
-	/* Context size is for future use. Right now, we only make sure
-	 * we are passed something we understand
-	 */
-	if (ctx_size < sizeof(struct ucontext))
+	unsigned long new_msr = 0;
+
+	if (new_ctx &&
+	    __get_user(new_msr, &new_ctx->uc_mcontext.gp_regs[PT_MSR]))
+		return -EFAULT;
+	if (/*
+	     * Check that the context is not smaller than the original
+	     * size (with VMX but without VSX)
+	     */
+		(ctx_size < UCONTEXTSIZEWITHOUTVSX) ||
+	    /*
+	     * If userspace doesn't provide enough room for VSX data,
+	     * but current thread has used VSX, we don't have anywhere
+	     * to store the full context back into.
+	     */
+		((ctx_size < sizeof(struct ucontext)) &&
+		 current->thread.used_vsr && old_ctx) ||
+	    /*
+	     * If the new context state sets the MSR VSX bits but
+	     * it doesn't provide VSX state.
+	     */
+		((ctx_size < sizeof(struct ucontext)) &&
+		 (new_msr & MSR_VSX)))
+		/* ... computer says "No" */
 		return -EINVAL;
 
 	if (old_ctx != NULL) {

  reply	other threads:[~2008-07-06  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04  8:25 powerpc: fix swapcontext backwards compatibility due to VSX ucontext changes Michael Neuling
2008-07-04 11:08 ` Paul Mackerras
2008-07-06  8:37   ` Michael Neuling [this message]
2008-07-08  8:43     ` [PATCH] " Michael Neuling

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=28458.1215333436@neuling.org \
    --to=mikey@neuling.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    /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;
as well as URLs for NNTP newsgroup(s).