On 12/21/18 1:40 AM, Greg KH wrote: > On Fri, Dec 21, 2018 at 07:57:21AM +1100, Dave Chinner wrote: >> On Thu, Dec 20, 2018 at 01:28:25PM +0100, Greg KH wrote: >>> On Thu, Dec 20, 2018 at 11:23:24PM +1100, Dave Chinner wrote: >>>> From: Dave Chinner <dchinner@xxxxxxxxxx> >>>> >>>> This reverts commit 61c6de667263184125d5ca75e894fcad632b0dd3. >> >> <snip> >> >>> <formletter> >>> >>> This is not the correct way to submit patches for inclusion in the >>> stable kernel tree. Please read: >>> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html >>> for how to do this properly. >>> >>> </formletter> >> >> This wasn't a stable kernel patch submission. This was to let the >> stable kernel maintainers know that a commit that was submitted for >> stable kernel inclusion (via a cc stable in the commit message) is >> buggy and should not be backported. i.e. if you've already queued/ >> backported 61c6de6672 then you need to drop it from your trees. > > As the commit 61c6de667263 ("fs/iomap.c: get/put the page in > iomap_page_create/release()") was tagged for a stable release (and is in > 4.19.11) it would be nice to also add the cc: stable in the revert. > When you just blindly send it to the stable mailing list, we have no > idea what to do with it, hence the automated form letter that was sent. > > Now that this is in Linus's tree, I'll dig out the revert and remember > to queue it up for the next round of stable updates, thanks for letting > us know. As a side note from an interested observer, I had no idea that patches from not-yet-released Linus kernels could make it into a "stable" kernel within 5 days of Linus' commit to an -rc. That seems shockingly fast, with very little margin for error. -Eric
