All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] resolve duplicate flag no for PG_lazyfree
Date: Mon, 14 May 2007 10:37:18 +0800	[thread overview]
Message-ID: <379110250.28666@ustc.edu.cn> (raw)
Message-ID: <20070514023718.GA14944@mail.ustc.edu.cn> (raw)

PG_lazyfree and PG_booked shares the same bit.

Either it is a bug that shall fixed by the following patch, or
the situation should be explicitly documented?

Signed-off-by: Fengguang Wu <wfg@mail.ustc.edu.cn>
---
 include/linux/page-flags.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-2.6.21-mm2.orig/include/linux/page-flags.h
+++ linux-2.6.21-mm2/include/linux/page-flags.h
@@ -91,7 +91,7 @@
 #define PG_buddy		19	/* Page is free, on buddy lists */
 #define PG_booked		20	/* Has blocks reserved on-disk */
 
-#define PG_lazyfree		20	/* MADV_FREE potential throwaway */
+#define PG_lazyfree		21	/* MADV_FREE potential throwaway */
 
 /* PG_owner_priv_1 users should have descriptive aliases */
 #define PG_checked		PG_owner_priv_1 /* Used by some filesystems */


             reply	other threads:[~2007-05-14  2:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14  2:37 Fengguang Wu [this message]
2007-05-14  2:37 ` [PATCH] resolve duplicate flag no for PG_lazyfree Fengguang Wu
2007-05-14  5:46   ` Andrew Morton
2007-05-14  5:46     ` Andrew Morton
2007-05-14  7:55     ` Fengguang Wu
2007-05-14  7:55       ` Fengguang Wu
2007-05-14  7:55         ` Fengguang Wu
2007-05-14 18:06     ` Theodore Tso
2007-05-14 18:06       ` Theodore Tso
2007-05-14 20:46       ` Andrew Morton
2007-05-14 20:46         ` Andrew Morton
2007-05-16  0:28         ` Nick Piggin
2007-05-16  0:28           ` Nick Piggin

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=379110250.28666@ustc.edu.cn \
    --to=fengguang.wu@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.