linux-kernel - m68k: default value for MEMORY

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: <a1c34f2b-115c-7ab9-5b69-7c11ebc18b4f@infradead.org>
Date:   Mon, 27 Sep 2021 14:26:45 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: m68k: default value for MEMORY_RESERVE?

Hi Geert,

Would it be safe (or unsafe) to add a default value for MEMORY_RESERVE?

As it is, kconfig can generate a randconfig with
"CONFIG_MEMORY_RESERVE=" (no value) since it has no default.

Then a following 'make all' finds an invalid symbol value and restarts
the config:

.config:214:warning: symbol value '' invalid for MEMORY_RESERVE
* Restart config...
Memory reservation (MiB) (MEMORY_RESERVE) [] (NEW)

That's OK until I try to script/automate randconfig builds.

Can we do anything about this or should I just add it to my
ignore-list?

thanks.
-- 
~Randy