From: James Hogan <james.hogan@imgtec.com>
To: James Cowgill <James.Cowgill@imgtec.com>
Cc: <linux-mips@linux-mips.org>, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH] MIPS: OCTEON: Fix copy_from_user fault handling for large buffers
Date: Mon, 9 Jan 2017 20:41:52 +0000 [thread overview]
Message-ID: <20170109204152.GA30210@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <ede411ad-ee19-e4e4-e6a2-585a85c640db@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 3397 bytes --]
On Mon, Jan 09, 2017 at 04:52:28PM +0000, James Cowgill wrote:
> If copy_from_user is called with a large buffer (>= 128 bytes) and the
> userspace buffer refers partially to unreadable memory, then it is
> possible for Octeon's copy_from_user to report the wrong number of bytes
> have been copied. In the case where the buffer size is an exact multiple
> of 128 and the fault occurs in the last 64 bytes, copy_from_user will
> report that all the bytes were copied successfully but leave some
> garbage in the destination buffer.
>
> The bug is in the main __copy_user_common loop in octeon-memcpy.S where
> in the middle of the loop, src and dst are incremented by 128 bytes. The
> l_exc_copy fault handler is used after this but that assumes that
> "src < THREAD_BUADDR($28)". This is not the case if src has already been
> incremented.
>
> Fix by adding an extra fault handler which rewinds the src and dst
> pointers 128 bytes before falling though to l_exc_copy.
>
> Thanks to the pwritev test from the strace test suite for originally
> highlighting this bug!
>
May I suggest adding:
Fixes: 5b3b16880f40 ("MIPS: Add Cavium OCTEON processor support ...")
> Signed-off-by: James Cowgill <James.Cowgill@imgtec.com>
> Cc: stable@vger.kernel.org
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Cc: linux-mips@linux-mips.org
Reviewed-by: James Hogan <james.hogan@imgtec.com>
Cheers
James
> ---
> arch/mips/cavium-octeon/octeon-memcpy.S | 20 ++++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/arch/mips/cavium-octeon/octeon-memcpy.S b/arch/mips/cavium-octeon/octeon-memcpy.S
> index 64e08df51d65..4668537b09c2 100644
> --- a/arch/mips/cavium-octeon/octeon-memcpy.S
> +++ b/arch/mips/cavium-octeon/octeon-memcpy.S
> @@ -208,18 +208,18 @@ EXC( STORE t2, UNIT(6)(dst), s_exc_p10u)
> ADD src, src, 16*NBYTES
> EXC( STORE t3, UNIT(7)(dst), s_exc_p9u)
> ADD dst, dst, 16*NBYTES
> -EXC( LOAD t0, UNIT(-8)(src), l_exc_copy)
> -EXC( LOAD t1, UNIT(-7)(src), l_exc_copy)
> -EXC( LOAD t2, UNIT(-6)(src), l_exc_copy)
> -EXC( LOAD t3, UNIT(-5)(src), l_exc_copy)
> +EXC( LOAD t0, UNIT(-8)(src), l_exc_copy_rewind16)
> +EXC( LOAD t1, UNIT(-7)(src), l_exc_copy_rewind16)
> +EXC( LOAD t2, UNIT(-6)(src), l_exc_copy_rewind16)
> +EXC( LOAD t3, UNIT(-5)(src), l_exc_copy_rewind16)
> EXC( STORE t0, UNIT(-8)(dst), s_exc_p8u)
> EXC( STORE t1, UNIT(-7)(dst), s_exc_p7u)
> EXC( STORE t2, UNIT(-6)(dst), s_exc_p6u)
> EXC( STORE t3, UNIT(-5)(dst), s_exc_p5u)
> -EXC( LOAD t0, UNIT(-4)(src), l_exc_copy)
> -EXC( LOAD t1, UNIT(-3)(src), l_exc_copy)
> -EXC( LOAD t2, UNIT(-2)(src), l_exc_copy)
> -EXC( LOAD t3, UNIT(-1)(src), l_exc_copy)
> +EXC( LOAD t0, UNIT(-4)(src), l_exc_copy_rewind16)
> +EXC( LOAD t1, UNIT(-3)(src), l_exc_copy_rewind16)
> +EXC( LOAD t2, UNIT(-2)(src), l_exc_copy_rewind16)
> +EXC( LOAD t3, UNIT(-1)(src), l_exc_copy_rewind16)
> EXC( STORE t0, UNIT(-4)(dst), s_exc_p4u)
> EXC( STORE t1, UNIT(-3)(dst), s_exc_p3u)
> EXC( STORE t2, UNIT(-2)(dst), s_exc_p2u)
> @@ -383,6 +383,10 @@ done:
> nop
> END(memcpy)
>
> +l_exc_copy_rewind16:
> + /* Rewind src and dst by 16*NBYTES for l_exc_copy */
> + SUB src, src, 16*NBYTES
> + SUB dst, dst, 16*NBYTES
> l_exc_copy:
> /*
> * Copy bytes from src until faulting load address (or until a
> --
> 2.11.0
>
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: James Cowgill <James.Cowgill@imgtec.com>
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH] MIPS: OCTEON: Fix copy_from_user fault handling for large buffers
Date: Mon, 9 Jan 2017 20:41:52 +0000 [thread overview]
Message-ID: <20170109204152.GA30210@jhogan-linux.le.imgtec.org> (raw)
Message-ID: <20170109204152.JzHeyfvlmbYXWBRrpCKMDwNsNxhW6uxlU-hPjOd1m1I@z> (raw)
In-Reply-To: <ede411ad-ee19-e4e4-e6a2-585a85c640db@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 3397 bytes --]
On Mon, Jan 09, 2017 at 04:52:28PM +0000, James Cowgill wrote:
> If copy_from_user is called with a large buffer (>= 128 bytes) and the
> userspace buffer refers partially to unreadable memory, then it is
> possible for Octeon's copy_from_user to report the wrong number of bytes
> have been copied. In the case where the buffer size is an exact multiple
> of 128 and the fault occurs in the last 64 bytes, copy_from_user will
> report that all the bytes were copied successfully but leave some
> garbage in the destination buffer.
>
> The bug is in the main __copy_user_common loop in octeon-memcpy.S where
> in the middle of the loop, src and dst are incremented by 128 bytes. The
> l_exc_copy fault handler is used after this but that assumes that
> "src < THREAD_BUADDR($28)". This is not the case if src has already been
> incremented.
>
> Fix by adding an extra fault handler which rewinds the src and dst
> pointers 128 bytes before falling though to l_exc_copy.
>
> Thanks to the pwritev test from the strace test suite for originally
> highlighting this bug!
>
May I suggest adding:
Fixes: 5b3b16880f40 ("MIPS: Add Cavium OCTEON processor support ...")
> Signed-off-by: James Cowgill <James.Cowgill@imgtec.com>
> Cc: stable@vger.kernel.org
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Cc: linux-mips@linux-mips.org
Reviewed-by: James Hogan <james.hogan@imgtec.com>
Cheers
James
> ---
> arch/mips/cavium-octeon/octeon-memcpy.S | 20 ++++++++++++--------
> 1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/arch/mips/cavium-octeon/octeon-memcpy.S b/arch/mips/cavium-octeon/octeon-memcpy.S
> index 64e08df51d65..4668537b09c2 100644
> --- a/arch/mips/cavium-octeon/octeon-memcpy.S
> +++ b/arch/mips/cavium-octeon/octeon-memcpy.S
> @@ -208,18 +208,18 @@ EXC( STORE t2, UNIT(6)(dst), s_exc_p10u)
> ADD src, src, 16*NBYTES
> EXC( STORE t3, UNIT(7)(dst), s_exc_p9u)
> ADD dst, dst, 16*NBYTES
> -EXC( LOAD t0, UNIT(-8)(src), l_exc_copy)
> -EXC( LOAD t1, UNIT(-7)(src), l_exc_copy)
> -EXC( LOAD t2, UNIT(-6)(src), l_exc_copy)
> -EXC( LOAD t3, UNIT(-5)(src), l_exc_copy)
> +EXC( LOAD t0, UNIT(-8)(src), l_exc_copy_rewind16)
> +EXC( LOAD t1, UNIT(-7)(src), l_exc_copy_rewind16)
> +EXC( LOAD t2, UNIT(-6)(src), l_exc_copy_rewind16)
> +EXC( LOAD t3, UNIT(-5)(src), l_exc_copy_rewind16)
> EXC( STORE t0, UNIT(-8)(dst), s_exc_p8u)
> EXC( STORE t1, UNIT(-7)(dst), s_exc_p7u)
> EXC( STORE t2, UNIT(-6)(dst), s_exc_p6u)
> EXC( STORE t3, UNIT(-5)(dst), s_exc_p5u)
> -EXC( LOAD t0, UNIT(-4)(src), l_exc_copy)
> -EXC( LOAD t1, UNIT(-3)(src), l_exc_copy)
> -EXC( LOAD t2, UNIT(-2)(src), l_exc_copy)
> -EXC( LOAD t3, UNIT(-1)(src), l_exc_copy)
> +EXC( LOAD t0, UNIT(-4)(src), l_exc_copy_rewind16)
> +EXC( LOAD t1, UNIT(-3)(src), l_exc_copy_rewind16)
> +EXC( LOAD t2, UNIT(-2)(src), l_exc_copy_rewind16)
> +EXC( LOAD t3, UNIT(-1)(src), l_exc_copy_rewind16)
> EXC( STORE t0, UNIT(-4)(dst), s_exc_p4u)
> EXC( STORE t1, UNIT(-3)(dst), s_exc_p3u)
> EXC( STORE t2, UNIT(-2)(dst), s_exc_p2u)
> @@ -383,6 +383,10 @@ done:
> nop
> END(memcpy)
>
> +l_exc_copy_rewind16:
> + /* Rewind src and dst by 16*NBYTES for l_exc_copy */
> + SUB src, src, 16*NBYTES
> + SUB dst, dst, 16*NBYTES
> l_exc_copy:
> /*
> * Copy bytes from src until faulting load address (or until a
> --
> 2.11.0
>
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-01-09 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 16:52 [PATCH] MIPS: OCTEON: Fix copy_from_user fault handling for large buffers James Cowgill
2017-01-09 16:52 ` James Cowgill
2017-01-09 18:53 ` David Daney
2017-01-09 18:53 ` David Daney
2017-01-09 20:41 ` James Hogan [this message]
2017-01-09 20:41 ` James Hogan
2017-02-11 21:30 ` James Hogan
2017-02-11 21:30 ` James Hogan
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=20170109204152.GA30210@jhogan-linux.le.imgtec.org \
--to=james.hogan@imgtec.com \
--cc=James.Cowgill@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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