[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090402095315.1098b6c3.akpm@linux-foundation.org>
Date: Thu, 2 Apr 2009 09:53:15 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Lee Schermerhorn <Lee.Schermerhorn@...com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
stable <stable@...nel.org>, Rik van Riel <riel@...hat.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
David Howells <dhowells@...hat.com>
Subject: Re: [PATCH] Define a UNIQUE value for AS_UNEVICTABLE flag
On Thu, 02 Apr 2009 12:47:15 -0400 Lee Schermerhorn <Lee.Schermerhorn@...com> wrote:
> [PATCH] Define UNIQUE value of AS_UNEVICTABLE
>
> Needed in 2.6.28, 2.6.29, ...
>
> A new "address_space flag"--AS_MM_ALL_LOCKS--was defined to use the next
> available AS flag while the Unevictable LRU was under development. The
> Unevictable LRU was using the same flag and "no one" noticed. Current
> mainline, since 2.6.28, has same value for two symbolic flag names.
argh.
What are the user-observable effects of the bug, and why didn't anyone
notice it until now?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists