linux-kernel - Re: [PATCH v2] arm64: defconfig: Enable zram, xfs and loading compressed FW support

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: Wed, 21 Feb 2024 16:14:21 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Maxime Ripard <mripard@...hat.com>
Cc: Javier Martinez Canillas <javierm@...hat.com>,
 linux-kernel@...r.kernel.org, Enric Balletbo i Serra <eballetbo@...hat.com>,
 Erico Nunes <nunes.erico@...il.com>, Brian Masney <bmasney@...hat.com>,
 Arnd Bergmann <arnd@...db.de>, Bjorn Andersson <quic_bjorande@...cinc.com>,
 Catalin Marinas <catalin.marinas@....com>,
 Geert Uytterhoeven <geert+renesas@...der.be>,
 Konrad Dybcio <konrad.dybcio@...aro.org>,
 Marek Szyprowski <m.szyprowski@...sung.com>,
 Neil Armstrong <neil.armstrong@...aro.org>, Will Deacon <will@...nel.org>,
 linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] arm64: defconfig: Enable zram, xfs and loading
 compressed FW support

On 21/02/2024 16:10, Krzysztof Kozlowski wrote:
> On 21/02/2024 15:48, Maxime Ripard wrote:
>> On Wed, Feb 21, 2024 at 03:22:38PM +0100, Krzysztof Kozlowski wrote:
>>> On 21/02/2024 15:13, Javier Martinez Canillas wrote:
>>>> These options are needed by some Linux distributions (e.g: Fedora), so
>>>
>>> How ZRAM is needed? Why Fedora cannot boot without it? Debian, which I
>>> use on my arm64 boards, does not have any problem.
>>
>> Is it relevant in any way?
> 
> Yes, because it is justification why we are doing it. Each commit is
> supposed to explain "why" and the explanation here is not enough.
> 
>>
>> I'm sure Debian can boot without MEMORY_HOTREMOVE, or BRIDGE, or
>> NUMA_BALANCING, or BPF_JIT, or NFS_FS, yet all of them are enabled. Let
>> me know if you want hundreds more examples.

BTW, each commit adding such options is supposed to explain why there
are needed, so please go to the git log and answer yourself why there
are there. I am pretty sure I will ack/review removal of every option
added without answering "why".

Don't twist the discussion of necessity of Kconfig options, because each
commit should stand on its own.

Best regards,
Krzysztof