linux-kernel - Re: linux-next: Fixes tag needs some work in the block tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48eff55b-f100-4057-8ff3-1d4b2089533d@kernel.dk>
Date: Thu, 13 Nov 2025 16:07:25 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Damien Le Moal <dlemoal@...nel.org>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the block tree

On 11/13/25 3:04 PM, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   7b2038b1b1d4 ("dm: fix zone reset all operation processing")
> 
> Fixes tag
> 
>   Fixes: db9aed869f34 ("block: introduce disk_report_zone()").
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: fdb9aed869f3 ("block: introduce disk_report_zone()")

Guys, that's now three funky shas that have never existed in my tree.
Can we please exercise a bit more diligence in actually tagging patches
correctly?

Stephen, can't sort them out now, as they are deeper in the stack. So I
guess we'll have to live with these two as well... And I guess I really
need to get my scripts setup to catch these kinds of errors, sadly.

-- 
Jens Axboe