From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 16 Oct 2007 17:28:53 -0400 From: Theodore Tso Subject: Re: [patch][rfc] rewrite ramdisk Message-ID: <20071016212853.GB1314@closure.lan> References: <200710151028.34407.borntraeger@de.ibm.com> <200710161808.06405.nickpiggin@yahoo.com.au> <200710161747.12968.nickpiggin@yahoo.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200710161747.12968.nickpiggin@yahoo.com.au> Sender: owner-linux-mm@kvack.org Return-Path: To: Nick Piggin Cc: "Eric W. Biederman" , Andrew Morton , Christian Borntraeger , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Martin Schwidefsky List-ID: On Tue, Oct 16, 2007 at 05:47:12PM +1000, Nick Piggin wrote: > + /* > + * ram device BLKFLSBUF has special semantics, we want to actually > + * release and destroy the ramdisk data. > + */ We won't be able to fix completely this for a while time, but the fact that BLKFLSBUF has special semantics has always been a major wart. Could we perhaps create a new ioctl, say RAMDISKDESTORY, and add a deperecation printk for BLKFLSBUF when passed to the ramdisk? I doubt there are many tools that actually take advantage of this wierd aspect of ramdisks, so hopefully it's something we could remove in a 18 months or so... - Ted -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org