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: <3459d7a5-f49c-4c5e-b010-a3732c3b0e00@kernel.org>
Date: Fri, 14 Nov 2025 08:38:04 +0900
From: Damien Le Moal <dlemoal@...nel.org>
To: Jens Axboe <axboe@...nel.dk>, Stephen Rothwell <sfr@...b.auug.org.au>
Cc: 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/14/25 8:07 AM, Jens Axboe wrote:
> 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?

My apologies about this. I was careful to take these from a fresh pull of
block/for-next but I obviously screwed-up the copy paste, missing the first
character.

> 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.

Stephen,

My apologies for the overhead.


-- 
Damien Le Moal
Western Digital Research