On Wed, May 10, 2023 at 06:09:35PM -0500, Linus Torvalds wrote: > On Wed, May 10, 2023 at 5:58 PM Greg Kroah-Hartman > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > Thanks! Turns out someone put the wrong "Fixes:" tag in that commit > > which is why I missed it. > > Hmm. Presumably the real commit ceeadb83aea2 at some point got > rebased, and had had that other mentioned SHA1 before that. > > It might be a good idea in general - not just for stable - if we had > some automation that said "this refers to a commit ID that doesn't > exist". We have that in linux-next today (or at least we used to, I took the scripts from linux-next and rely on them to catch this in my trees.) I cleaned up the scripts and posted them to the kernel workgroup mailing list a long time ago for any other maintainer to also use, I've attached it below as well. I run across this issue 2-3 times each -rc release, it's quite common but very low overall. thanks, greg k-h
Attachment:
verify_fixes.sh
Description: Bourne shell script
