From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <1373658551.17876.117.camel@gandalf.local.home> Subject: Re: [ 00/19] 3.10.1-stable review From: Steven Rostedt To: Theodore Ts'o Cc: Guenter Roeck , Linus Torvalds , Greg Kroah-Hartman , Dave Jones , Linux Kernel Mailing List , Andrew Morton , stable Date: Fri, 12 Jul 2013 15:49:11 -0400 In-Reply-To: <20130712193557.GB342@thunk.org> References: <20130711214830.611455274@linuxfoundation.org> <20130711222935.GA11340@redhat.com> <20130711224455.GA17222@kroah.com> <20130712141530.GA3629@roeck-us.net> <20130712173150.GA5534@roeck-us.net> <20130712181103.GA6689@roeck-us.net> <20130712193557.GB342@thunk.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On Fri, 2013-07-12 at 15:35 -0400, Theodore Ts'o wrote: > So the problem is that maintainers are lazy. They don't want to go > back for bug fixes that have "proven" themselves, and even if they > aren't critical bug fixes, they are things which a distro maintainer > or a stable kernel user might want (and sometimes stable uers are > uppity enough to expect subsystem maintainers to do this back > porting). So subsystem maintainers then react by marking submits for > stable even though they really should soak for a release or two before > submitting them, since by marking them as submit, the commit gets > pushed to stable automatically --- albeit early. Actually, this is a very good point. There were one or two stable patches I had pushed to linux-next that I wasn't too comfortable about. If the fix goes back to older trees, I rather have them stirring in linux-next and push it in the next merge window instead of pushing it to Linus and have it go to stable immediately. Unless its a obvious fix, I tend to take about a month from the time I get a stable fix to the time I push it out. Making sure the stable fix doesn't introduce new bugs. -- Steve