linux-kernel - Question about reference to config KERNEL_6

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

Message-ID: <CAKXUXMyfrM6amOR7Ysim3WNQ-Ckf9HJDqRhAoYmLXujo1UV+yA@mail.gmail.com>
Date: Wed, 17 Jan 2024 09:37:31 +0100
From: Lukas Bulwahn <lukas.bulwahn@...il.com>
To: Johannes Berg <johannes.berg@...el.com>, Gregory Greenman <gregory.greenman@...el.com>, 
	linux-wireless <linux-wireless@...r.kernel.org>
Cc: Kalle Valo <kvalo@...nel.org>, kernel-janitors <kernel-janitors@...r.kernel.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Question about reference to config KERNEL_6_2

Dear Johannes, dear Gregory,

I am a kernel janitor checking for issues in kernel build config
options in the repository. Amongst others, I check for references to
config options that have not been defined anywhere in the tree using
an existing script in the repository,
/scripts/checkkconfigsymbols.py.

At the beginning of this year, I checked which issues were introduced
in 2023 and were not yet resolved by others or my janitor work
throughout the year. In other words, looking at some issues that
simply slipped through last year.

Commit ffbd0c8c1e7f ("wifi: mac80211: add an element parsing unit
test") and commit 730eeb17bbdd ("wifi: cfg80211: add first kunit
tests, for element defrag") add new configs that depend on
!KERNEL_6_2, but the config option KERNEL_6_2 does not exist in the
tree.

Also, Kalle Valo [1] asked during patch review about that, but did not
get any response on the mailing list.

So, what is the KERNEL_6_2 option all about? Is this something that
was just used locally for early development?

Can we just delete this dependency in these two config options?

If so, I will gladly send a patch for that.

[1] https://lore.kernel.org/all/877cp6q7ws.fsf@kernel.org/

Best regards,

Lukas