1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC

  • Bug#1106035: [Pkg-zfsonlinux-devel] Bug#1106035: zfs: Upstream patch fo

    From Florian Bach@21:1/5 to All on Mon May 19 19:40:02 2025
    Am 19.05.25 um 07:46 schrieb Antonio Russo:

    There is progress on this, but it is occurring in real time.  My suggestion is to wait for upstream to decide they understand it, finalize the PR,
    merge
    it, and then back port the fix to 2.3.  This last step may be painful,
    since
    the analysis may have to be re-done on the early state of the code in 2.3.

    The fix has just been merged into master so it seems like upstream
    thinks it's finalized enough.

    As for backporting, should be fairly easy. I took a look at the affected
    file, and that file (or at least the related code) hasn't been modified
    since it was introduced 6 years ago, so should be fairly simple to
    backport to whatever version, even way back to 2.0.0 if necessary.
    Unless I'm missing something?


    I would recommend reducing the severity of this bug to important so that
    zfs is not removed from trixie.

    I thought a bug with potential data loss would be correctly classified
    as "grave", but I don't know much about how Debian usually handles
    situations like these where the bug has existed for a long time already.
    I'm happy to downgrade this to important (if necessary) if the package
    will be removed from trixie otherwise. But right now, at least to me,
    there should still be enough time to get this fixed, right?

    Best,
    Florian Bach

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Leseratte10@vodafone.de@21:1/5 to All on Wed May 21 16:30:01 2025
    On Tue, 20 May 2025 05:54:30 -0600 Antonio Russo wrote:
    See also [1], which presumably will cherry-pick the fix onto 2.2
    without changes. If that is indeed the case, we should probably
    cherry pick it as is, too.

    One of the other patches referenced in that discussion ([1]) should
    probably be included as well. Either as part of a 2.3.3 release (if that happens soon enough) or as a debian patch. That patch is basically the
    same error (mismatch between dsl_dataset_rele and
    dsl_dataset_rele_flags) as the one that's confirmed to cause the data corruption, just in another location (so it might be causing other
    corruption elsewhere) and it's also mentioned for inclusion in 2.2.8.

    Best,
    Florian

    [1] https://github.com/openzfs/zfs/pull/17353

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Florian Bach@21:1/5 to All on Sat Jun 21 14:30:01 2025
    Is there any update about this bug report yet? Will the fix be
    backported to the current release or will zfs 2.3.3 still make it into
    trixie?

    ZFS 2.3.3 which includes all these fixes has been released last
    Thursday. Is there any work being done either getting this version
    packaged, or back-porting the bugfixes?

    In its current state, zfs would get autoremoved on July 2nd, so either a backport or a new release is needed until then, or the severity needs to
    be reduced (which is a solution I don't really like).

    Best,
    Florian

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)