Bug#1073979: Please consider enabling the dm-clone module (CONFIG_DM_CLONE)

To: Rob Leslie <rob@mars.org>
Cc: 1073979@bugs.debian.org
Subject: Bug#1073979: Please consider enabling the dm-clone module (CONFIG_DM_CLONE)
From: Salvatore Bonaccorso <carnil@debian.org>
Date: Sun, 4 May 2025 23:27:56 +0200
Message-id: <[🔎] aBfb3CUfgpLNL4_k@eldamar.lan>
Reply-to: Salvatore Bonaccorso <carnil@debian.org>, 1073979@bugs.debian.org
In-reply-to: <aBUEEVGaAh4_JaFB@mars.org>
References: <aBUEEVGaAh4_JaFB@mars.org> <20240620222636.1C79B19C5D8@atreus.mars.org>

Control: tags -1 + moreinfo

Hi Rob,

On Fri, May 02, 2025 at 10:42:41AM -0700, Rob Leslie wrote:
> reopen 948782
> severity 948782 wishlist

Thanks for following up on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073979#12

this misses some explanations. DM_CLONE is still marked experimental
(since the initial commit and never got removed) upstream, can you
elaborate why it is believed we should enable this despite in the
Debian provided kernel?

Regards,
Salvatore

Reply to:

Prev by Date: Bug#1087748: linux-image-6.12-rc6-amd64: xHCI host not responding to stop endpoint command
Next by Date: Processed: Re: Please consider enabling the dm-clone module (CONFIG_DM_CLONE)
Previous by thread: Bug#1087748: linux-image-6.12-rc6-amd64: xHCI host not responding to stop endpoint command
Next by thread: Processed: Re: Please consider enabling the dm-clone module (CONFIG_DM_CLONE)
Index(es):
- Date
- Thread