From: Michael Ellerman <mpe@ellerman.id.au>
To: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: powerpc/mm: Allow user space to map rtas_rmo_buf
Date: Fri, 29 Jan 2016 12:58:40 +1100 (AEDT) [thread overview]
Message-ID: <20160129015840.7EADC1402AC@ozlabs.org> (raw)
In-Reply-To: <1453392931-20707-1-git-send-email-hegdevasant@linux.vnet.ibm.com>
On Thu, 2016-21-01 at 16:15:31 UTC, Vasant Hegde wrote:
> With commit 90a545e9 (restrict /dev/mem to idle io memory ranges) mapping
> rtas_rmo_buf from user space is failing. Hence we are not able to make
> RTAS syscall.
>
> This patch calls page_is_rtas_user_buf before calling iomem_is_exclusive
> in devmem_is_allowed(). This will allow user space to map rtas_rmo_buf
> and we are able to make RTAS syscall.
>
> Reported-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> CC: Dan Williams <dan.j.williams@intel.com>
> CC: Nathan Fontenot <nfont@linux.vnet.ibm.com>
> CC: Michael Ellerman <mpe@ellerman.id.au>
> Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
> Acked-by: Dan Williams <dan.j.williams@intel.com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/e256caa7d0515e301f8c8c6e7d
cheers
prev parent reply other threads:[~2016-01-29 1:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 16:15 [PATCH] powerpc/mm: Allow user space to map rtas_rmo_buf Vasant Hegde
2016-01-21 16:32 ` Dan Williams
2016-01-22 5:29 ` Michael Ellerman
2016-01-22 6:28 ` Vasant Hegde
2016-01-22 8:35 ` Michael Ellerman
2016-01-22 10:41 ` Denis Kirjanov
2016-01-25 18:42 ` Nathan Fontenot
2016-01-25 18:42 ` Nathan Fontenot
2016-01-29 1:58 ` Michael Ellerman [this message]
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=20160129015840.7EADC1402AC@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=dan.j.williams@intel.com \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@linux.vnet.ibm.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).