On 2012.10.05 at 08:37 -0700, Greg Kroah-Hartman wrote: > On Fri, Oct 05, 2012 at 05:29:48PM +0200, Borislav Petkov wrote: > > On Fri, Oct 05, 2012 at 07:26:39AM -0700, Greg Kroah-Hartman wrote: > > > I don't have a problem with this patch, but I don't understand why > > > it's now showing up. There haven't been any changes in the ratelimit.h > > > area recently that I can see, so why is this change needed now? What > > > is in the tty layer that is causing this, just the fact that it's > > > actually being used now? > > > > >From my quick semi-skilled git history browsing, I'd say it's > > 5d4121c04b357 which added the WARN_RATELIMIT to tty_init_dev during the > > current merge window. > > So WARN_RATELIMIT was never working properly? If so, how far back does > it go in kernel releases that this should be fixed?
The only user until this merge window was net/core/filter.c. The WARN_RATELIMIT is used there since v3.0. -- Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
