linux-kernel - linux-next: Fixes tag needs some work in the perf-current 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-next>] [day] [month] [year] [list]

Message-ID: <20240902081837.6def2734@canb.auug.org.au>
Date: Mon, 2 Sep 2024 08:18:37 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>, Namhyung Kim
 <namhyung@...nel.org>
Cc: Veronika Molnarova <vmolnaro@...hat.com>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>
Subject: linux-next: Fixes tag needs some work in the perf-current tree

Hi all,

In commit

  387ad33e5410 ("perf test pmu: Set uninitialized PMU alias to null")

Fixes tag

  Fixes: 3e0bf9 ("perf pmu: Restore full PMU name wildcard support")

has these problem(s):

  - Target SHA1 does not exist

Actually, the quoted SHA1 is too short and is ambiguous in my tree:

$ git show 3e0bf9
error: short object ID 3e0bf9 is ambiguous
hint: The candidates are:
hint:   3e0bf9fde298 commit 2024-06-26 - perf pmu: Restore full PMU name wildcard support
hint:   3e0bf93e0354 tree
fatal: ambiguous argument '3e0bf9': unknown revision or path not in the working tree.

so you should use

Fixes: 3e0bf9fde298 ("perf pmu: Restore full PMU name wildcard support")

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped