[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <94540d05-12ab-49b8-9e37-04a29f5cdf77@vasilevsky.ca>
Date: Mon, 26 Aug 2024 02:03:44 -0400
From: Dave Vasilevsky <dave@...ilevsky.ca>
To: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
Michael Ellerman <mpe@...erman.id.au>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: bhe@...hat.com, linuxppc-dev@...ts.ozlabs.org, linux-sh@...r.kernel.org,
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-26 01:38, John Paul Adrian Glaubitz wrote:
> On Mon, 2024-08-26 at 12:02 +1000, Michael Ellerman wrote:
>> So IMHO having it enabled by default in upstream does make sense,
>> because it more closely matches what distros/users actually run.
>
> Well, at least Debian did not enable it by default as otherwise we wouldn't
> have noticed this change downstream.
Debian does enable it explicitly on some supported architectures, but not all: https://salsa.debian.org/search?group_id=2107&nav_source=navbar&project_id=18670&repository_ref=master&scope=blobs&search=path%3Aconfig+CRASH_DUMP&search_code=true
By my count, 6.9's new default affected mips, powerpc (32-bit), riscv, and sh in Debian.
-Dave
Powered by blists - more mailing lists