linux-kernel - Re: About the .scmversion removal (commit f6e09b07cc12)

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]

Date:   Fri, 10 Mar 2023 09:51:54 +0900
From:   Masahiro Yamada <masahiroy@...nel.org>
To:     "Guilherme G. Piccoli" <gpiccoli@...lia.com>
Cc:     linux-kbuild@...r.kernel.org, nathan@...nel.org,
        rasmus.villemoes@...vas.dk,
        Nick Desaulniers <ndesaulniers@...gle.com>, nicolas@...sle.eu,
        linux-kernel <linux-kernel@...r.kernel.org>,
        "Guilherme G. Piccoli" <kernel@...ccoli.net>
Subject: Re: About the .scmversion removal (commit f6e09b07cc12)

On Fri, Mar 10, 2023 at 6:15 AM Guilherme G. Piccoli
<gpiccoli@...lia.com> wrote:
>
> Hi Masahiro / all, I was rebuilding the kernel today, just adding some
> debug statements, when I noticed a lot of stuff got built again. I was
> using ".scmversion" to prevent UTS version changes, so only affected
> files got indeed rebuilt.
>
> After commit f6e09b07cc12 ("kbuild: do not put .scmversion into the
> source tarball"), seems this file is automatically deleted and I'm not
> sure how should I proceed to continue with the same behavior.
>
> Apologies if this is a silly question, any advice is much appreciated!
> Also, I've CCed all the emails from [0], so apologies if anybody looped
> here shouldn't be CCed.


Not a silly question, but .scmversion was intended for source
package creation (deb, rpm) in my understanding.

If you want to use a fixed string for the UTS version,
please pass KERNELRELEASE=<some-string> to the build command line.






-- 
Best Regards
Masahiro Yamada