Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754262AbYKFAwe (ORCPT ); Wed, 5 Nov 2008 19:52:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751870AbYKFAw0 (ORCPT ); Wed, 5 Nov 2008 19:52:26 -0500 Received: from ozlabs.org ([203.10.76.45]:56098 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752044AbYKFAwZ (ORCPT ); Wed, 5 Nov 2008 19:52:25 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18706.16317.759662.855430@cargo.ozlabs.ibm.com> Date: Thu, 6 Nov 2008 11:52:13 +1100 From: Paul Mackerras To: Andreas Schwab Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Fix msr check in compat_sys_swapcontext In-Reply-To: References: X-Mailer: VM 8.0.9 under Emacs 22.2.1 (i486-pc-linux-gnu) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1138 Lines: 37 Andreas Schwab writes: > The new context may not be 16-byte aligned, so the real address of the > mcontext structure should be read from the uc_regs pointer instead of > directly using the (unaligned) uc_mcontext field. Good catch, but... > @@ -941,9 +941,17 @@ long sys_swapcontext(struct ucontext __user *old_ctx, > #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 (new_ctx) { > + struct mcontext __user *mcp; > + u32 cmcp; > + > + /* Get pointer to the real mcontext. */ > + if (__get_user(cmcp, &new_ctx->uc_regs)) we need to use get_user, not __get_user, since we haven't done an access_ok() check on the address. > + return -EFAULT; > + mcp = (struct mcontext __user *)(u64)cmcp; > + if (__get_user(new_msr, &mcp->mc_gregs[PT_MSR])) ditto here. Paul. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/