Re: FAILED: patch "[PATCH] ext4: fix off by one issue in" failed to apply to 6.4-stable tree

[Greg KH <gregkh@linuxfoundation.org>]

On Tue, Aug 22, 2023 at 02:46:38PM +0530, Ojaswin Mujoo wrote:
> On Mon, Jul 24, 2023 at 08:17:57AM +0200, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 6.4-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> > 
> > To reproduce the conflict and resubmit, you may use the following commands:
> > 
> > git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.4.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x 5d5460fa7932bed3a9082a6a8852cfbdb46acbe8
> > # <resolve conflicts, build, test, etc.>
> > git commit -s
> > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2023072456-starting-gauging-768c@gregkh' --subject-prefix 'PATCH 6.4.y' HEAD^..
> > 
> > Possible dependencies:
> > 
> > 
> > 
> > thanks,
> > 
> > greg k-h
> 
> 
> Hi Greg, Ted,
> 
> Sorry for being late on this, I was off for a good part of this month.
> 
> So i got multiple such FAILUREs from different stable trees for this
> particular patch (linked at end), but seems like these trees don't even
> have the patch pointed by Fixes tag.
> 
> Although we can safely ignore backporting this, I just wanted to check
> why did I get these false failures so I can avoid it in the future.
> I was thinking that we would automatically check the fixes tag to see
> which trees need the backport? Is that not the case?

The fixes tag in this commit:
	> > Fixes: 33122aa930 ("ext4: Add allocation criteria 1.5 (CR1_5)")

References a commit id that is not in Linus's tree, so I have to guess.

Please use valid git ids in your Fixes: line and this will not happen in
the future.

thanks,

greg k-h