linux-kernel - Re: [PATCH] selftests: vDSO: don't include generated headers for chacha test

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: <ZuGUpjOwE-f4YWUn@zx2c4.com>
Date: Wed, 11 Sep 2024 15:01:26 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Mark Brown <broonie@...nel.org>
Cc: Aishwarya TCV <aishwarya.tcv@....com>, adhemerval.zanella@...aro.org,
	linux-kernel@...r.kernel.org,
	Naresh Kamboju <naresh.kamboju@...aro.org>
Subject: Re: [PATCH] selftests: vDSO: don't include generated headers for
 chacha test

On Wed, Sep 11, 2024 at 02:47:02PM +0200, Jason A. Donenfeld wrote:
> On Wed, Sep 11, 2024 at 11:14:06AM +0100, Mark Brown wrote:
> > On Wed, Sep 11, 2024 at 04:44:48AM +0200, Jason A. Donenfeld wrote:
> > > On Tue, Sep 10, 2024 at 11:52:51PM +0100, Aishwarya TCV wrote:
> > > > make[4]: *** [Makefile:299:
> > > > /tmp/kci/linux/build/kselftest/kvm/aarch64/aarch32_id_regs.o] Error 1
> > > > make[4]: Leaving directory '/tmp/kci/linux/tools/testing/selftests/kvm'
> > 
> > > You sure this bisected right? That directory isn't related to the
> > > commit in question, I don't think...
> > 
> > I eyeballed it for Aishwarya and it looked related on first glance
> > (messing around with the generated headers), though looking again it's
> > only in the vDSO directory so shouldn't be messing up other
> > directories...
> 
> Okay, so... I reproduced the problem on linux-next. Then I reverted the
> commit and reproduced it again. Then just to be sure, I ran:
> 
>     $ git checkout v6.9 tools/testing/selftests/vDSO/
> 
> And then I reproduced the problem again.
> 
> So I think we can be somewhat certain the unrelated directory is indeed
> unrelated.

Ahhh, got it.

Running `$ rm tools/include/asm/sysreg-defs.h` fixes the problem. I'll
look into a fix this afternoon.

Jason