linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Julia Lawall <julia@diku.dk>
Cc: linux-mm@kvack.org
Subject: Re: question about nommu.c
Date: Fri, 14 Aug 2009 04:57:39 +0900	[thread overview]
Message-ID: <20090813195738.GA8686@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0908132136540.7209@ask.diku.dk>

On Thu, Aug 13, 2009 at 09:41:38PM +0200, Julia Lawall wrote:
> The function vmalloc_user in the file mm/nommu.c contains the following 
> code:
> 
> struct vm_area_struct *vma;
> ...
> if (vma)
>         vma->vm_flags |= VM_USERMAP;
> 
> The constant VM_USERMAP, however, is elsewhere used in a structure of type 
> vm_struct, not vm_area_struct.  Furthermore, the value of VM_USERMAP is 8, 
> which is the same as the value of VM_SHARED (define in mm.h), which is 
> elsewhere used with a vm_area_struct structure.  Is this occurrence of 
> VM_USERMAP correct?  Or should it be VM_SHARED?  Or should it be something 
> else?
> 
Yes, this is currently broken, albeit generally harmless. I've been
working on cleaning this up, but have not gotten around to posting
patches yet.

Part of this requires building on top of the infrastructure we have in
place with the vm_regions to layer a proper vmap implementation on top
of, which should in turn restore some meaning to the vmlist and permit
struct vm_struct to be used on nommu properly.

At the moment this is not a big problem as it doesn't really impact
anything, it's more regarding future directions for the nommu memory
management code.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-08-13 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 19:41 Julia Lawall
2009-08-13 19:57 ` Paul Mundt [this message]
2009-08-13 20:32   ` Julia Lawall

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=20090813195738.GA8686@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=julia@diku.dk \
    --cc=linux-mm@kvack.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