linux-kernel - Re: [PATCH] crash: Default to CRASH_DUMP=n when support for it is unlikely

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]

Message-ID: <1568b378-5592-4d23-a572-4e09f3996331@vasilevsky.ca>
Date: Thu, 29 Aug 2024 23:37:29 -0400
From: Dave Vasilevsky <dave@...ilevsky.ca>
To: Baoquan He <bhe@...hat.com>
Cc: glaubitz@...sik.fu-berlin.de, linuxppc-dev@...ts.ozlabs.org,
 linux-sh@...r.kernel.org, mpe@...erman.id.au, kexec@...ts.infradead.org,
 linux-kernel@...r.kernel.org, Reimar Döffinger
 <Reimar.Doeffinger@....de>
Subject: Re: [PATCH] crash: Default to CRASH_DUMP=n when support for it is
 unlikely

On 2024-08-29 23:15, Baoquan He wrote:
>> +config ARCH_DEFAULT_CRASH_DUMP
>> +	def_bool n
> 
> If we don't add ARCH_DEFAULT_CRASH_DUMP at all in sh arch, the
> CRASH_DUMP will be off by default according to the below new definition
> of CRASH_DUMP?

Yes, that's true. But if we don't add it at all in sh arch, it looks confusing
in the search feature of menuconfig:

> Symbol: ARCH_DEFAULT_CRASH_DUMP [=ARCH_DEFAULT_CRASH_DUMP]
> Type  : unknown

So I thought it was better to explicitly set it to 'n'. What do you think?

-Dave