[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0901301323040.3150@localhost.localdomain>
Date: Fri, 30 Jan 2009 13:25:41 -0800 (PST)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Hugh Dickins <hugh@...itas.com>
cc: Lee Schermerhorn <Lee.Schermerhorn@...com>,
Greg KH <gregkh@...e.de>,
Maksim Yevmenkin <maksim.yevmenkin@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Nick Piggin <npiggin@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
will@...wder-design.com, Rik van Riel <riel@...hat.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Mikos Szeredi <miklos@...redi.hu>
Subject: Re: [PATCH] Fix OOPS in mmap_region() when merging adjacent VM_LOCKED
file segments
On Fri, 30 Jan 2009, Hugh Dickins wrote:
>
> But I'm caring more about that VM_ACCOUNT...
The bright side here is that I think the VM_ACCOUNT bit differences only
really happen for MAP_SHARED file mappings. For MAP_SHARED anon mappings
we already don't share (for other reasons), and for private mappings
VM_ACCOUNT looks stable (ie it's reliably either set or not, and stays
that way).
So the impact is reasonably low. But it would definitely be good to clean
up that whole VM_ACCOUNT logic, and incidentally then fix that merging
issue at the same time.
Linus
--
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