From: Julia Lawall <julia@diku.dk>
To: linux-mm@kvack.org
Subject: question about nommu.c
Date: Thu, 13 Aug 2009 21:41:38 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0908132136540.7209@ask.diku.dk> (raw)
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?
julia
--
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>
next reply other threads:[~2009-08-13 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 19:41 Julia Lawall [this message]
2009-08-13 19:57 ` Paul Mundt
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=Pine.LNX.4.64.0908132136540.7209@ask.diku.dk \
--to=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