linux-kernel - Re: [PATCH][RFT] Re: linux-next: build failure after merge of the perf 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] [day] [month] [year] [list]

Date: Thu, 18 Apr 2024 22:06:46 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>,
	Namhyung Kim <namhyung@...nel.org>, Ian Rogers <irogers@...gle.com>,
	Kan Liang <kan.liang@...el.com>,
	Adrian Hunter <adrian.hunter@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: [PATCH][RFT] Re: linux-next: build failure after merge of the
 perf tree

On Thu, Apr 18, 2024 at 09:54:03PM -0300, Arnaldo Carvalho de Melo wrote:
> On Fri, Apr 19, 2024 at 09:17:17AM +1000, Stephen Rothwell wrote:
> > On Thu, 18 Apr 2024 18:31:45 -0300 Arnaldo Carvalho de Melo <acme@...nel.org> wrote:
> > > And reproduced the problem, find below a patch that reverts the patch
> > > that removes tools/include/uapi/linux/stat.h, with it applied in the
> > > sequence above right after the merge of perf-tools-next it seems to
> > > work, i.e. it builds without problems.

> > > Can you please test this so that I can get it into perf-tools-next?

> > That works for me.  Thanks for this.

> > Tested-by: Stephen Rothwell <sfr@...b.auug.org.au> # PowerPC le incermental build

> > I will apply that patch to linux-next today (if you don't have time to
> > update your tree before I merge it).

> I'm finishing some local tests here, will push perf-tools-next after
> that, some 30 minutes.

Ah, and again thanks for the report and follow up collaboration on
having these things sorted out, I'm sorry for not having this fixed
sooner, I'm taking notes to automate this type of test and have it done
before pushing branches publicly.

I just found it strange that when trying to reproduce this the problem
didn't manifested itself reliably, but then, ENOTIME to root cause this
so far, this (partial) revert is the best thing we can do now, so lets
go with it.

- Arnaldo