• Bug#1073979: Please consider enabling the dm-clone module (CONFIG_DM_CL

    From Salvatore Bonaccorso@21:1/5 to Rob Leslie on Sun May 4 23:40:01 2025
    XPost: linux.debian.kernel

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rob Leslie@21:1/5 to All on Mon May 5 22:00:02 2025
    XPost: linux.debian.kernel

    Hi Salvatore,

    Thanks for the follow-up.

    On May 4, 2025, at 4:27 PM, Salvatore Bonaccorso <carnil@debian.org> wrote:

    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?


    DM_CLONE is useful to have available in certain circumstances. I have successfully used it more than once over the years to do live data migrations. It was a hassle to build custom kernels just for this, but in the end quite worth it. Having DM_CLONE
    available as a module in Debian by default would greatly simplify the lives of others finding themselves in similar situations. The fact that more than one bug was filed requesting it shows there is interest.

    Although marked experimental, I have experienced no problems with it. I note that DM_CACHE is also marked experimental, yet already enabled in Debian despite this.

    Thanks for your consideration.

    --
    Rob Leslie
    rob@mars.org



    <html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi Salvatore,<div><br></div><div>Thanks for the follow-up.</div><div><
    </div><div><blockquote type="cite"><div>On May 4, 2025, at 4:27 PM, Salvatore Bonaccorso &lt;carnil@debian.org&gt; wrote:</div><br class="Apple-interchange-newline"><div>Thanks for following up on<br>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
    1073979#12<br><br>this misses some explanations. DM_CLONE is still marked experimental<br>(since the initial commit and never got removed) upstream, can you<br>elaborate why it is believed we should enable this despite in the<br>Debian provided kernel?<
    </div></blockquote></div><div><div><br></div></div><div>DM_CLONE is useful to have available in certain circumstances. I have successfully used it more than once over the years to do live data migrations. It was a ha