linux-kernel - Re: [GIT PULL] x86/entry for 7.0-rc1

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: <712d7389-d744-4e0d-a1a3-2b938de55aaa@zytor.com>
Date: Wed, 11 Feb 2026 09:39:13 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] x86/entry for 7.0-rc1

On 2026-02-11 09:05, Linus Torvalds wrote:
> 
> I often actually look at the build results. Not the object files, no.
> But I do things like
> 
>    make xyz/file.s
> 
> *ALL* the time when developing, and I just don't want to have to treat
> the "this was what I just generated" and "this was what I generated it
> from" as something very different.
> 
> Admittedly, these days I don't do much actual development, so I guess
> I wouldn't care.
> 
> Which reminds me that I need to go back to merging...
> 

Oh, I do too. And so I do make in the build directory, or tack on the O=
option. FAR more annoying to me is that kbuild requires you to do the make
command in the root directory of the tree.

"make -C ../../../../.. arch/x86/entry/vdso/vdso32/sigreturn.o" is not really
much better than

"make -C ../../../../.. O=o/x86_64.cf arch/x86/entry/vdso/vdso32/sigreturn.o"

Come to think of it, I really should just wrap that up in a script...

If anyone is interested, my scripts are sitting at:

	git://git.zytor.com/linux/ktest.git

	-hpa