stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tip-bot for CQ Tang <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
	cq.tang@intel.com, stable@vger.kernel.org, tglx@linutronix.de,
	mike.marciniszyn@intel.com, hpa@linux.intel.com
Subject: [tip:x86/urgent] x86-64: Fix the failure case in copy_user_handle_tail()
Date: Mon, 18 Mar 2013 13:05:25 -0700	[thread overview]
Message-ID: <tip-66db3feb486c01349f767b98ebb10b0c3d2d021b@git.kernel.org> (raw)
In-Reply-To: <20130318150221.8439.993.stgit@phlsvslse11.ph.intel.com>

Commit-ID:  66db3feb486c01349f767b98ebb10b0c3d2d021b
Gitweb:     http://git.kernel.org/tip/66db3feb486c01349f767b98ebb10b0c3d2d021b
Author:     CQ Tang <cq.tang@intel.com>
AuthorDate: Mon, 18 Mar 2013 11:02:21 -0400
Committer:  H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Mon, 18 Mar 2013 11:32:03 -0700

x86-64: Fix the failure case in copy_user_handle_tail()

The increment of "to" in copy_user_handle_tail() will have incremented
before a failure has been noted.  This causes us to skip a byte in the
failure case.

Only do the increment when assured there is no failure.

Signed-off-by: CQ Tang <cq.tang@intel.com>
Link: http://lkml.kernel.org/r/20130318150221.8439.993.stgit@phlsvslse11.ph.intel.com
Signed-off-by: Mike Marciniszyn <mike.marciniszyn@intel.com>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Cc: <stable@vger.kernel.org>
---
 arch/x86/lib/usercopy_64.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/lib/usercopy_64.c b/arch/x86/lib/usercopy_64.c
index 05928aa..906fea3 100644
--- a/arch/x86/lib/usercopy_64.c
+++ b/arch/x86/lib/usercopy_64.c
@@ -74,10 +74,10 @@ copy_user_handle_tail(char *to, char *from, unsigned len, unsigned zerorest)
 	char c;
 	unsigned zero_len;
 
-	for (; len; --len) {
+	for (; len; --len, to++) {
 		if (__get_user_nocheck(c, from++, sizeof(char)))
 			break;
-		if (__put_user_nocheck(c, to++, sizeof(char)))
+		if (__put_user_nocheck(c, to, sizeof(char)))
 			break;
 	}
 

           reply	other threads:[~2013-03-18 20:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20130318150221.8439.993.stgit@phlsvslse11.ph.intel.com>]

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-66db3feb486c01349f767b98ebb10b0c3d2d021b@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=cq.tang@intel.com \
    --cc=hpa@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mike.marciniszyn@intel.com \
    --cc=mingo@kernel.org \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).