Safely removing mmaped files [LWN.net]

From:		ebiederm@xmission.com (Eric W. Biederman)
To:		Andrew Morton <akpm@linux-foundation.org>
Subject:		[PATCH 0/4] Safely removing mmaped files
Date:		Fri, 04 Sep 2009 12:24:44 -0700
Message-ID:		<m1fxb2wm0z.fsf@fess.ebiederm.org>
Cc:		<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>, Alexey Dobriyan <adobriyan@gmail.com>, Greg Kroah-Hartman <gregkh@suse.de>, Tejun Heo <tj@kernel.org>
Archive-link:		Article, Thread


Currently when mmaped files are removed I have not found a single
instance in the kernel where we handle it correctly.  Frequently after
a hot remove we will either leak a file (with weird ensuing
consequences) or we will goof and not call vm_ops->close() which can
cause leaks.

It turns out this problem isn't too bad to actually fix and this
patchset is my generic solution.  Tested against 2.6.31-rc8 with a
process that mmaped /sys/*/*/resource0 and /proc/bus/pci/*/*.

I'm not certain what the best way to carry these patches is to get
them merged.  Andrew can you carry this patchset?


Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/