> From: Valdis.Kletnieks@xxxxxx [mailto:Valdis.Kletnieks@xxxxxx] > Sent: Friday, February 11, 2011 2:53 PM > To: akpm@xxxxxxxxxxxxxxxxxxxx; Dan Magenheimer > Cc: mm-commits@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; linux- > mm@xxxxxxxxx; linux-fsdevel@xxxxxxxxxxxxxxx > Subject: Re: mmotm 2011-02-10-16-26 uploaded > > On Thu, 10 Feb 2011 16:26:36 PST, akpm@xxxxxxxxxxxxxxxxxxxx said: > > The mm-of-the-moment snapshot 2011-02-10-16-26 has been uploaded to > > > > http://userweb.kernel.org/~akpm/mmotm/ > > CONFIG_ZCACHE=m dies a horrid death: Thanks Valdis. A fix for this has already been posted by Nitin Gupta and Randy Dunlap here: https://lkml.org/lkml/2011/2/10/383 Another patch for a zcache memory leak has been posted here: https://lkml.org/lkml/2011/2/10/306 I'm sorry that multiple people have run into this in multiple trees. I have to admit I am a bit baffled as to what the proper tree flow is for bug fixes like this, but would be happy to "follow the process" if I am told what it is or if someone can point me to a document describing it. (Clearly making sure there are no bugs at all in a submission is the best way to go, but I'm afraid I can't claim to be perfect :-) Thanks, Dan P.S. I suppose there isn't really a good reason for CONFIG_ZCACHE to be tri-state as it really makes no sense as a module because, if CONFIG_CLEANCACHE is enabled, it will always get loaded. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
