linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Elie De Brauwer <eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 3/3] mem.4: Add CONFIG_STRICT_DEVMEM
Date: Tue, 06 Jan 2015 11:50:28 +0100	[thread overview]
Message-ID: <54ABBDF4.4030902@gmail.com> (raw)
In-Reply-To: <1420204298-25625-4-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 01/02/2015 02:11 PM, Elie De Brauwer wrote:
> Since 2.6.26 the CONFIG_NONPROMISC_DEVMEM options limits the physical
> addresses which can be accessed through /dev/mem.

Thanks, Elie. Applied.

Cheers,

Michael


> Sources:
>  - Changelog: http://kernelnewbies.org/Linux_2_6_26
>  - Initial commit: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ae531c26c5c2a28ca1b35a75b39b3b256850f2c8
>  - Rename of name: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d092633bff3b19faffc480fe9810805e7792a029
> 
> Signed-off-by: Elie De Brauwer <eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
>  man4/mem.4 | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/man4/mem.4 b/man4/mem.4
> index 6688345..372d4fa 100644
> --- a/man4/mem.4
> +++ b/man4/mem.4
> @@ -23,7 +23,7 @@
>  .\" %%%LICENSE_END
>  .\"
>  .\" Modified Sat Jul 24 16:59:10 1993 by Rik Faith (faith-+5Oa3zvhR2o3uPMLIKxrzw@public.gmane.org)
> -.TH MEM 4 1992-11-21 "Linux" "Linux Programmer's Manual"
> +.TH MEM 4 2015-01-02 "Linux" "Linux Programmer's Manual"
>  .SH NAME
>  mem, kmem, port \- system memory, kernel memory and system ports
>  .SH DESCRIPTION
> @@ -40,6 +40,13 @@ References to nonexistent locations cause errors to be returned.
>  Examining and patching is likely to lead to unexpected results
>  when read-only or write-only bits are present.
>  .LP
> +Since 2.6.26, and depending on the architecture, the
> +.B CONFIG_STRICT_DEVMEM
> +kernel configuration option limits the areas
> +which can be accessed through this file.
> +For example: on x86, RAM access is not allowed but accessing
> +memory-mapped PCI regions is.
> +.LP
>  It is typically created by:
>  .RS
>  .sp
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2015-01-06 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 13:11 [PATCH 0/3] mem.4 updates Elie De Brauwer
     [not found] ` <1420204298-25625-1-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-02 13:11   ` [PATCH 1/3] mem.4: /dev/kmem depends on CONFIG_DEVKMEM Elie De Brauwer
     [not found]     ` <1420204298-25625-2-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-06 10:41       ` Michael Kerrisk (man-pages)
2015-01-02 13:11   ` [PATCH 2/3] mem.4: correct /dev/port group in example Elie De Brauwer
     [not found]     ` <1420204298-25625-3-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-06 10:44       ` Michael Kerrisk (man-pages)
2015-01-02 13:11   ` [PATCH 3/3] mem.4: Add CONFIG_STRICT_DEVMEM Elie De Brauwer
     [not found]     ` <1420204298-25625-4-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-06 10:50       ` Michael Kerrisk (man-pages) [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=54ABBDF4.4030902@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).