On Wed, Oct 16, 2013 at 08:08:09AM -0400, Theodore Ts'o wrote: > On Mon, Oct 14, 2013 at 02:15:53PM -0700, Greg KH wrote: > > > This patch adds a new interface which allows architecture-specific > > > code to address a security issue with the random driver for those > > > platforms which define get_cycles() to return zero all the time. The > > > most important p[latform for this is MIPS, since there are a lot of > > > home routers which use MIPS, but the full list is: > > > > But, what code is using that interface? Adding new features and > > interfaces is not for stable kernel releases, is it? > > > > If no one is using this new interface, why add it? > > The code to use it is coming in the MIPS tree, and there was work that > I expect would use it for 68k tree coming soon. Since it was a more > substantial changes, I'm not surprised that it hasn't flowed into > mainline yet, but I expect that it would during the next merge window. > I pushed the interface pre-merge window due to the recent kvetching > over too many patches that were targetted for the stable kernel > showing up during the merge window. Since this was a low-risk patch, > I decided to push it to Linus early. That's fine to push it to Linus, but for stable, I can't take new "features" without any user of those calls, that wouldn't make sense, would it? How about when those MIPS changes get to Linus, you let stable@xxxxxxxxxxxxxxx know about it, and let me know this original commit id as well, and both can be added then? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html