From: James Hogan <james.hogan@imgtec.com>
To: linux-metag@vger.kernel.org
Cc: Al Viro <viro@zeniv.linux.org.uk>,
James Hogan <james.hogan@imgtec.com>,
stable@vger.kernel.org
Subject: [PATCH 0/2] metag/uaccess: Some more user access fixes
Date: Tue, 2 May 2017 22:11:53 +0100 [thread overview]
Message-ID: <cover.e98ed86557d7dd12941799c9c2d31dd7d3bda36d.1493759289.git-series.james.hogan@imgtec.com> (raw)
Here are a couple more user access fixes for metag. The first fixes
access_ok() which was flawed in a number of ways (including ignoring the
size of the copy and so allowing a copy crossing the user/kernel
boundary). The second adds missing access_ok() checking to
strncpy_from_user(). Thanks to Al for spotting some of the issues.
Both are tagged for stable.
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-metag@vger.kernel.org
Cc: stable@vger.kernel.org
James Hogan (2):
metag/uaccess: Fix access_ok()
metag/uaccess: Check access_ok in strncpy_from_user
arch/metag/include/asm/uaccess.h | 49 ++++++++++++++++++++-------------
1 file changed, 31 insertions(+), 18 deletions(-)
--
git-series 0.8.10
next reply other threads:[~2017-05-02 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 21:11 James Hogan [this message]
[not found] ` <cover.e98ed86557d7dd12941799c9c2d31dd7d3bda36d.1493759289.git-series.james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2017-05-02 21:11 ` [PATCH 1/2] metag/uaccess: Fix access_ok() James Hogan
[not found] ` <8a8b56638bcac4e64cccc88bf95a0f9f4b19a2fb.1493759289.git-series.james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2017-05-02 21:26 ` James Hogan
[not found] ` <20170502212605.GO1105-4bYivNCBEGTR3KXKvIWQxtm+Uo4AYnCiHZ5vskTnxNA@public.gmane.org>
2017-05-02 21:36 ` Stephen Rothwell
2017-05-02 21:11 ` [PATCH 2/2] metag/uaccess: Check access_ok in strncpy_from_user 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=cover.e98ed86557d7dd12941799c9c2d31dd7d3bda36d.1493759289.git-series.james.hogan@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=linux-metag@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).