From bugtracker-admin at leaf.dragonflybsd.org Tue Apr 8 01:39:26 2025 From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org) Date: Tue, 08 Apr 2025 01:39:26 -0700 Subject: [DragonFlyBSD - Bug #3359] Too many zlib References: Message-ID: Issue #3359 has been updated by liweitianux. tkusumi wrote: > Recently added hammer2(8) recover directive has added yet another zlib to HAMMER2, this time in userspace. > This is a third copy of zlib in HAMMER2 related source. > Why not just use contrib/zlib-1.2, or if not possible why ? Some time ago I discussed this with dillon on IRC, he insisted that HAMMER2 bundle its own zlib (and well tested) in order to keep HAMMER2 self-contained. Nevertheless, he agreed that the userland HAMMER2 utilities (such as hammer2(8) and makefs(8)) could just reuse the in-kernel HAMMER2's zlib copy. > hammer2(8) recover directive has also added a userspace copy of LZ4. > This one can easily reuse sys/vfs/hammer2/*lz4*. > All we need is a few KERNEL ifdefs around malloc/free related and header includes. Hmm, I suggest we do the same as zlib above. Meanwhile, it's better to reorganize the LZ4 code similar to vfs/hammer2/xxhash. In addition, there is also the @zlib@ kernel module compiled from @sys/net/zlib at . I'd like it to reuse the source from @contrib/zlib at . We can refer to FreeBSD for this change. ---------------------------------------- Bug #3359: Too many zlib http://bugs.dragonflybsd.org/issues/3359#change-14582 * Author: tkusumi * Status: New * Priority: Normal * Target version: 6.6 * Start date: 2023-10-18 ---------------------------------------- Recently added hammer2(8) recover directive has added yet another zlib to HAMMER2, this time in userspace. This is a third copy of zlib in HAMMER2 related source. Why not just use contrib/zlib-1.2, or if not possible why ? hammer2(8) recover directive has also added a userspace copy of LZ4. This one can easily reuse sys/vfs/hammer2/*lz4*. All we need is a few KERNEL ifdefs around malloc/free related and header includes. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account From bugtracker-admin at leaf.dragonflybsd.org Tue Apr 8 01:41:59 2025 From: bugtracker-admin at leaf.dragonflybsd.org (bugtracker-admin at leaf.dragonflybsd.org) Date: Tue, 08 Apr 2025 01:41:59 -0700 Subject: [DragonFlyBSD - Bug #3281] (Resolved) Crash after leaving unattended for a while References: Message-ID: Issue #3281 has been updated by liweitianux. Status changed from New to Resolved % Done changed from 0 to 100 Fixed by commit 9e15d348daf953250c9873368a19011e150af3d8 on 2025-02-22. ---------------------------------------- Bug #3281: Crash after leaving unattended for a while http://bugs.dragonflybsd.org/issues/3281#change-14583 * Author: bhaible * Status: Resolved * Priority: Normal * Category: Kernel * Target version: 6.4 * Start date: 2021-06-14 ---------------------------------------- I left a DragonFly BSD 6.0 VM (VirtualBox) unattended for a couple of days, with no load (just a shell prompt sitting there). The kernel crashed. See the attached screenshot. ---Files-------------------------------- dragonfly60-crash1.png (7.87 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account