linux-kernel - [PATCH] kbuild: optimize the increments the version number rules

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>] [day] [month] [year] [list]

Message-Id: <20230216084209.4783-1-tangmeng@uniontech.com>
Date:   Thu, 16 Feb 2023 16:42:09 +0800
From:   Meng Tang <tangmeng@...ontech.com>
To:     masahiroy@...nel.org, linux-kernel@...r.kernel.org
Cc:     Meng Tang <tangmeng@...ontech.com>
Subject: [PATCH] kbuild: optimize the increments the version number rules

Currently, the build version of the kernel can only count integers.
If the user defines that the version in .version is a non-integer
number, the build version will be '1'.

The original intention of the version rule as I understand it is to
initialize the version to '1' when the user does not define a build
version.

In order to allow users to define a non-integer kernel version, and
it will not be automatically changed to '1' after definition, this
modification is submitted

Fixes: 2df8220cc511 ("kbuild: build init/built-in.a just once")

Signed-off-by: Meng Tang <tangmeng@...ontech.com>
---
 init/build-version | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/init/build-version b/init/build-version
index 537d45815083..ca985dc285cc 100755
--- a/init/build-version
+++ b/init/build-version
@@ -3,7 +3,12 @@
 
 prev_ver=$(cat .version 2>/dev/null) &&
 ver=$(expr ${prev_ver} + 1 2>/dev/null) ||
-ver=1
+if [ X$prev_ver = "X" ]
+then
+	ver=1
+else
+	ver=$prev_ver
+fi
 
 echo ${ver} > .version
 
-- 
2.20.1