From: Linus Torvalds <torvalds@linux-foundation.org>
To: Paul Burton <paul.burton@mips.com>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
Paul Burton <pburton@wavecomp.com>
Subject: Re: [PATCH] MIPS: Fix access_ok() for the last byte of user space
Date: Sat, 9 Feb 2019 12:06:46 -0800 [thread overview]
Message-ID: <CAHk-=wgnfMwrP-KRGKW76uE1jBdDae6auRMke+tFmz5shvkvYA@mail.gmail.com> (raw)
In-Reply-To: <20190209194718.1294-1-paul.burton@mips.com>
On Sat, Feb 9, 2019 at 11:47 AM Paul Burton <paul.burton@mips.com> wrote:
>
> Fix MIPS in the same way as alpha & SH, by subtracting one from the addr
> + size condition when size is non-zero. With this the access_ok() calls
> above return 1 indicating that the access may be valid.
You might want to update the comment above that thing too..
Linus
next prev parent reply other threads:[~2019-02-09 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 19:47 [PATCH] MIPS: Fix access_ok() for the last byte of user space Paul Burton
2019-02-09 20:06 ` Linus Torvalds [this message]
2019-04-14 20:16 ` Philippe Mathieu-Daudé
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='CAHk-=wgnfMwrP-KRGKW76uE1jBdDae6auRMke+tFmz5shvkvYA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=pburton@wavecomp.com \
/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).