From: kanoj@google.engr.sgi.com (Kanoj Sarcar)
To: linux-mm@kvack.org
Cc: torvalds@transmeta.com
Subject: [PATCH] kanoj-mm4.0-2.2.9 Free up VM_GROWSUP for new use
Date: Mon, 31 May 1999 12:39:27 -0700 (PDT) [thread overview]
Message-ID: <199905311939.MAA77710@google.engr.sgi.com> (raw)
It seems to me that the flag bit VM_GROWSUP is not set anywhere.
Seeing that the vm_flags bits are nearly all taken, it is probably
worthwhile to free up this bit for new usage. Here's the patch to
do that.
Thanks.
Kanoj
kanoj@engr.sgi.com
--- arch/mips/kernel/irixelf.c Mon May 31 12:21:02 1999
+++ irixelf.c1 Mon May 31 12:22:16 1999
@@ -1050,7 +1050,7 @@
if (!(vma->vm_flags & (VM_READ|VM_WRITE|VM_EXEC)))
return 0;
#if 1
- if (vma->vm_flags & (VM_WRITE|VM_GROWSUP|VM_GROWSDOWN))
+ if (vma->vm_flags & (VM_WRITE|VM_GROWSDOWN))
return 1;
if (vma->vm_flags & (VM_READ|VM_EXEC|VM_EXECUTABLE|VM_SHARED))
return 0;
--- fs/binfmt_elf.c Mon May 31 12:20:57 1999
+++ binfmt_elf.c1 Mon May 31 12:22:02 1999
@@ -960,7 +960,7 @@
if(vma->vm_flags & VM_IO)
return 0;
#if 1
- if (vma->vm_flags & (VM_WRITE|VM_GROWSUP|VM_GROWSDOWN))
+ if (vma->vm_flags & (VM_WRITE|VM_GROWSDOWN))
return 1;
if (vma->vm_flags & (VM_READ|VM_EXEC|VM_EXECUTABLE|VM_SHARED))
return 0;
--- mm.h Mon May 31 12:20:50 1999
+++ mm.h1 Mon May 31 12:26:08 1999
@@ -73,7 +73,7 @@
#define VM_MAYSHARE 0x0080
#define VM_GROWSDOWN 0x0100 /* general info on the segment */
-#define VM_GROWSUP 0x0200
+#define VM_notused 0x0200 /* this flagbit free for any use */
#define VM_SHM 0x0400 /* shared memory area, don't swap out */
#define VM_DENYWRITE 0x0800 /* ETXTBSY on write attempts.. */
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
reply other threads:[~1999-05-31 19:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199905311939.MAA77710@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.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