From: Andrew Morton <akpm@osdl.org>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH 1/2] NOMMU: Set BDI capabilities for /dev/mem and /dev/kmem
Date: Tue, 29 Aug 2006 11:20:30 -0700 [thread overview]
Message-ID: <20060829112030.a2a8c763.akpm@osdl.org> (raw)
In-Reply-To: <20060829175949.32281.21374.stgit@warthog.cambridge.redhat.com>
On Tue, 29 Aug 2006 18:59:49 +0100
David Howells <dhowells@redhat.com> wrote:
> From: David Howells <dhowells@redhat.com>
>
> Set the backing device info capabilities for /dev/mem and /dev/kmem to permit
> direct sharing under no-MMU conditions.
>
> Also comment the capabilities for /dev/zero.
>
> Signed-Off-By: David Howells <dhowells@redhat.com>
> ---
>
> drivers/char/mem.c | 42 ++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 42 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/char/mem.c b/drivers/char/mem.c
> index 917b204..4c29619 100644
> --- a/drivers/char/mem.c
> +++ b/drivers/char/mem.c
> @@ -238,6 +238,19 @@ #endif
> }
> #endif
>
> +#ifndef CONFIG_MMU
> +static unsigned long get_unmapped_area_mem(struct file *file,
> + unsigned long addr,
> + unsigned long len,
> + unsigned long pgoff,
> + unsigned long flags)
> +{
> + if (!valid_mmap_phys_addr_range(pgoff, len))
> + return (unsigned long) -EINVAL;
> + return pgoff;
> +}
#else
#define get_unmapped_area_mem NULL
#endif
> @@ -782,6 +801,9 @@ static const struct file_operations mem_
> .write = write_mem,
> .mmap = mmap_mem,
> .open = open_mem,
> +#ifndef CONFIG_MMU
> + .get_unmapped_area = get_unmapped_area_mem,
> +#endif
> };
zap ifdefs.
> static const struct file_operations kmem_fops = {
> @@ -790,6 +812,9 @@ static const struct file_operations kmem
> .write = write_kmem,
> .mmap = mmap_kmem,
> .open = open_kmem,
> +#ifndef CONFIG_MMU
> + .get_unmapped_area = get_unmapped_area_mem,
> +#endif
> };
Ditto.
> +/*
> + * capabilities for /dev/zero
> + * - permits private mappings, "copies" are taken of the source of zeros
> + */
> static struct backing_dev_info zero_bdi = {
> .capabilities = BDI_CAP_MAP_COPY,
> };
>
> +/*
> + * capabilities for /dev/mem and /dev/kmem
> + * - permits shared mmap for read, write and/or exec
> + * - does not permit private mmap (add BDI_CAP_MAP_COPY to permit this)
> + */
> +static struct backing_dev_info mem_bdi = {
> + .capabilities = (BDI_CAP_MAP_DIRECT |
> + BDI_CAP_READ_MAP | BDI_CAP_WRITE_MAP |
> + BDI_CAP_EXEC_MAP),
> +};
This changes behaviour, doesn't it? But only for !CONFIG_MMU kernels?
Perhaps some additional commentary around this is needed.
> static const struct file_operations full_fops = {
> .llseek = full_lseek,
> .read = read_full,
> @@ -861,9 +901,11 @@ static int memory_open(struct inode * in
> {
> switch (iminor(inode)) {
> case 1:
> + filp->f_mapping->backing_dev_info = &mem_bdi;
> filp->f_op = &mem_fops;
> break;
> case 2:
> + filp->f_mapping->backing_dev_info = &mem_bdi;
> filp->f_op = &kmem_fops;
> break;
> case 3:
Perhaps one could make mem_bdi==NULL if !CONFIG_MMU, for a minor space
saving.
next prev parent reply other threads:[~2006-08-29 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 17:59 David Howells
2006-08-29 17:59 ` [PATCH 2/2] NOMMU: Check that access_process_vm() has a valid target David Howells
2006-08-29 18:20 ` Andrew Morton [this message]
2006-08-29 18:39 ` [PATCH 1/2] NOMMU: Set BDI capabilities for /dev/mem and /dev/kmem David Howells
2006-08-29 19:28 ` Andrew Morton
2006-08-30 8:38 ` David Howells
2006-08-30 15:05 ` Andrew Morton
2006-08-30 9:24 ` David Howells
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=20060829112030.a2a8c763.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=uclinux-dev@uclinux.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
all inboxes | Powered by JetHome®