linux-kernel - Re: linux-next: Fixes tag needs some work in the mm-unstable 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: <CABFDxMHSkmH3LLmZYZN6-Ymj+yRNoaA3=9zg=4P7ZrOxrBs8bg@mail.gmail.com>
Date: Tue, 19 Aug 2025 09:59:20 +0900
From: Sang-Heon Jeon <ekffu200098@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Andrew Morton <akpm@...ux-foundation.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux Next Mailing List <linux-next@...r.kernel.org>, SeongJae Park <sj@...nel.org>
Subject: Re: linux-next: Fixes tag needs some work in the mm-unstable tree

Hello, Stephen

On Tue, Aug 19, 2025 at 6:24 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
>   1ce24beaff3f ("selftests/damon: change wrong json.dump usage to json.dumps")
>
> Fixes tag
>
>   Fixes: 441f487d6ebf ("selftests/damon: test no-op commit broke DAMON status")
>
> has these problem(s):
>
>   - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: a0b60d083fb6 ("selftests/damon: test no-op commit broke DAMON status")

You're right. I think it might be changed at the point rc1 -> rc2 on
the mm tree.
Is there anything I can do? Or maybe Andrew can help?

I didn't mean to bother you guys.  Also, original patch is from here [1]

[1] https://lore.kernel.org/all/20250816014033.190451-1-ekffu200098@gmail.com/

> --
> Cheers,
> Stephen Rothwell

Best Regards
Sang-Heon Jeon