linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ley Foon Tan <lftan@altera.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	"nios2-dev@lists.rocketboards.org"
	<nios2-dev@lists.rocketboards.org>
Subject: Re: [PATCH v2 02/11] nios2: Export strncpy_from_user / strnlen_user to modules
Date: Mon, 10 Aug 2015 16:10:44 +0800	[thread overview]
Message-ID: <CAFiDJ59myj9n5wwYaMWK9aYnwhKS-mOovaCx=bJ+mHtNecC5Dw@mail.gmail.com> (raw)
In-Reply-To: <1438960924-23628-3-git-send-email-james.hogan@imgtec.com>

On Fri, Aug 7, 2015 at 11:21 PM, James Hogan <james.hogan@imgtec.com> wrote:
> Update the nios2 architecture code to export strncpy_from_user() and
> strnlen_user() to modules. The test_user_copy module will soon test
> them.
>
> Signed-off-by: James Hogan <james.hogan@imgtec.com>
> Cc: Ley Foon Tan <lftan@altera.com>
> Cc: nios2-dev@lists.rocketboards.org
> ---
>  arch/nios2/mm/uaccess.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/arch/nios2/mm/uaccess.c b/arch/nios2/mm/uaccess.c
> index 7663e156ff4f..ecd8b122948b 100644
> --- a/arch/nios2/mm/uaccess.c
> +++ b/arch/nios2/mm/uaccess.c
> @@ -146,6 +146,7 @@ long strncpy_from_user(char *__to, const char __user *__from, long __len)
>                 l--;
>         return l;
>  }
> +EXPORT_SYMBOL(strncpy_from_user);
>
>  long strnlen_user(const char __user *s, long n)
>  {
> @@ -161,3 +162,4 @@ long strnlen_user(const char __user *s, long n)
>         }
>         return n + 1;
>  }
> +EXPORT_SYMBOL(strnlen_user);

Acked-by: Ley Foon Tan <lftan@altera.com>

  reply	other threads:[~2015-08-10  8:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 15:21 [PATCH v2 00/11] test_user_copy improvements James Hogan
2015-08-07 15:21 ` [PATCH v2 01/11] microblaze: Export __strnlen_user to modules James Hogan
2015-08-07 15:21 ` [PATCH v2 02/11] nios2: Export strncpy_from_user / strnlen_user " James Hogan
2015-08-10  8:10   ` Ley Foon Tan [this message]
2015-08-07 15:21 ` [PATCH v2 03/11] openrisc: Export __clear_user " James Hogan
2015-08-07 15:21 ` [PATCH v2 04/11] xtensa: Export __strnlen_user " James Hogan
2015-08-07 15:21 ` [PATCH v2 05/11] test_user_copy: Check legit kernel accesses James Hogan
2015-08-07 15:21 ` [PATCH v2 06/11] test_user_copy: Check unchecked accessors James Hogan
2015-08-07 15:22 ` [PATCH v2 07/11] test_user_copy: Check __copy_{to,from}_user_inatomic() James Hogan
2015-08-07 15:22 ` [PATCH v2 08/11] test_user_copy: Check __clear_user()/clear_user() James Hogan
2015-08-07 15:22 ` [PATCH v2 09/11] test_user_copy: Check user string accessors James Hogan
2015-08-07 15:22 ` [PATCH v2 10/11] test_user_copy: Check user compatibility accessors James Hogan
2015-08-07 15:22 ` [PATCH v2 11/11] test_user_copy: Check user checksum functions James Hogan
2015-08-07 23:51 ` [PATCH v2 00/11] test_user_copy improvements Kees Cook
2015-08-10 22:29 ` David Miller
2015-08-11  4:08   ` David Miller
2015-08-11 11:20     ` Geert Uytterhoeven
2015-08-12 21:34       ` David Miller
2015-08-11 11:07   ` James Hogan
2015-08-11 17:32     ` David Miller

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='CAFiDJ59myj9n5wwYaMWK9aYnwhKS-mOovaCx=bJ+mHtNecC5Dw@mail.gmail.com' \
    --to=lftan@altera.com \
    --cc=james.hogan@imgtec.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nios2-dev@lists.rocketboards.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).