From: Michal Hocko <mhocko@suse.cz>
To: Chen Gang <gang.chen.5i5j@gmail.com>
Cc: 管雪涛 <gxt@pku.edu.cn>, "Guan Xuetao" <gxt@mprc.pku.edu.cn>,
akpm@linux-foundation.org, liuj97@gmail.com, rientjes@google.com,
dhowells@redhat.com, mgorman@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] arch:unicore32:mm: add devmem_is_allowed() to support STRICT_DEVMEM
Date: Wed, 16 Apr 2014 11:05:11 +0200 [thread overview]
Message-ID: <20140416090511.GB12866@dhcp22.suse.cz> (raw)
In-Reply-To: <534C899A.2020008@gmail.com>
On Tue 15-04-14 09:21:30, Chen Gang wrote:
[...]
> diff --git a/arch/unicore32/include/asm/io.h b/arch/unicore32/include/asm/io.h
> index 39decb6..ae327e4 100644
> --- a/arch/unicore32/include/asm/io.h
> +++ b/arch/unicore32/include/asm/io.h
There is already quite a mess where the function is defined. We have it
in mmap.c, init.c, mem.c and s390 defines it in page.h. Is there any
good reason to add yet another place and pull in additional header files
dependencies?
Why not follow x86 here? Or even better git rid of the code duplication
and provide generic implementation which different arches can reuse and
extend? arm{64}, unicore32 seem to be identical. Powepc and x86 have an
additional test to the core one used by the above arches. Only tile
seems to be be doing something completely different.
> @@ -44,5 +44,28 @@ extern void __uc32_iounmap(volatile void __iomem *addr);
> #define PIO_MASK (unsigned int)(IO_SPACE_LIMIT)
> #define PIO_RESERVED (PIO_OFFSET + PIO_MASK + 1)
>
> +#ifdef CONFIG_STRICT_DEVMEM
> +
> +#include <linux/ioport.h>
> +#include <linux/mm.h>
> +
> +/*
> + * devmem_is_allowed() checks to see if /dev/mem access to a certain
> + * address is valid. The argument is a physical page number.
> + * We mimic x86 here by disallowing access to system RAM as well as
> + * device-exclusive MMIO regions. This effectively disable read()/write()
> + * on /dev/mem.
> + */
> +static inline int devmem_is_allowed(unsigned long pfn)
> +{
> + if (iomem_is_exclusive(pfn << PAGE_SHIFT))
> + return 0;
> + if (!page_is_ram(pfn))
> + return 1;
> + return 0;
> +}
> +
> +#endif /* CONFIG_STRICT_DEVMEM */
> +
> #endif /* __KERNEL__ */
> #endif /* __UNICORE_IO_H__ */
> --
> 1.7.9.5
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2014-04-16 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 11:28 [PATCH] " Chen Gang
2014-04-08 3:20 ` 回复: " 管雪涛
2014-04-08 4:54 ` Chen Gang
2014-04-15 0:14 ` Chen Gang
2014-04-15 0:28 ` [PATCH v2] " Chen Gang
2014-04-15 0:42 ` Chen Gang
2014-04-15 1:21 ` [PATCH v3] " Chen Gang
2014-04-16 5:15 ` 回复: " 管雪涛
2014-04-16 5:43 ` Chen Gang
2014-04-16 9:05 ` Michal Hocko [this message]
2014-04-16 10:11 ` Chen Gang
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=20140416090511.GB12866@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=gxt@pku.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=mgorman@suse.de \
--cc=rientjes@google.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
all inboxes | Powered by JetHome®