linux-kernel - Re: [GIT PULL] perf tools fixes for v6.8

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: <CAHk-=wgVxsBrf9hme-VQ+h+h6j3V9n_ph0ALT1EANDiEKy3uHg@mail.gmail.com>
Date: Thu, 1 Feb 2024 13:21:16 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Ingo Molnar <mingo@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, Jiri Olsa <jolsa@...nel.org>, 
	Namhyung Kim <namhyung@...nel.org>, Ian Rogers <irogers@...gle.com>, 
	Adrian Hunter <adrian.hunter@...el.com>, Clark Williams <williams@...hat.com>, 
	Kate Carcia <kcarcia@...hat.com>, linux-kernel@...r.kernel.org, 
	linux-perf-users@...r.kernel.org, James Clark <james.clark@....com>, 
	Kan Liang <kan.liang@...ux.intel.com>, Sun Haiyong <sunhaiyong@...ngson.cn>, 
	Thomas Richter <tmricht@...ux.ibm.com>, Yanteng Si <siyanteng@...ngson.cn>, 
	Yicong Yang <yangyicong@...ilicon.com>, Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [GIT PULL] perf tools fixes for v6.8

On Thu, 1 Feb 2024 at 13:14, Arnaldo Carvalho de Melo <acme@...nel.org> wrote:
>
> I should've known better and not send the noisy JSON changes at this
> point in time.

Arnaldo, it's not the JSON changes in the history.

It's the absolute garbage in the *tag* itself. It's crazy. Do this"

   git fetch   git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git
perf-tools-fixes-for-v6.8-1-2024-02-01

   git cat-file tag FETCH_HEAD

and see complete and utter garbage in the tag contents.

Note: that is not a change *made* by the tag. It's literally just
garbage content in the tag *message* itself.

You have something *seriously* wrong with your scripting or tag
creation workflow.

               Linus