On Wednesday 17 October 2007 07:28, Theodore Tso wrote: > 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...
It would be nice to be able to do that, I agree. The new ramdisk code will be able to flush the buffer cache and destroy its data separately, so it can actually be implemented. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
