Er G9q9JUQS4kePGUq/7co5dsDskkgfHE+r/G53JMGrjX0VOrV4jTCwZvxMlnAgozNnbB1CeM /N/d5tIxekGGl6xrX8WTIDfJUDhq59o6DO5dnt9OeFepc388V9SxxGJC1+6PpQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z2VQC4M04zk5G for ; Tue, 25 Feb 2025 21:01:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 51PL1NpD079078 for ; Tue, 25 Feb 2025 21:01:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 51PL1NKv079077 for bugs@FreeBSD.org; Tue, 25 Feb 2025 21:01:23 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 282576] Memory leak in sysctlbyname FreeBSD 14.1-RELEASE-p5 GENERIC x64 Date: Tue, 25 Feb 2025 21:01:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Security X-Bugzilla-Component: Base X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: markj@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to resolution cc bug_status Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282576 Mark Johnston changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|secteam@FreeBSD.org |bugs@FreeBSD.org Resolution|--- |Not A Bug CC| |markj@FreeBSD.org Status|New |Closed --- Comment #2 from Mark Johnston --- markj@xinde> valgrind -s ./a.out=20 =3D=3D21570=3D=3D Memcheck, a memory error detector =3D=3D21570=3D=3D Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward = et al. =3D=3D21570=3D=3D Using Valgrind-3.24.0 and LibVEX; rerun with -h for copyr= ight info =3D=3D21570=3D=3D Command: ./a.out =3D=3D21570=3D=3D=20 FreeBSD Kernel Version: FreeBSD 15.0-CURRENT #322 main-n275473-5778cbdae761: Sun Feb 16 05:03:29 UTC 2025 root@pkg-main:/usr/obj/root/freebsd/amd64.amd64/sys/GENERIC-NODEBUG =3D=3D21570=3D=3D=20 =3D=3D21570=3D=3D HEAP SUMMARY: =3D=3D21570=3D=3D in use at exit: 4,096 bytes in 1 blocks =3D=3D21570=3D=3D total heap usage: 2 allocs, 1 frees, 4,251 bytes alloca= ted =3D=3D21570=3D=3D=20 =3D=3D21570=3D=3D LEAK SUMMARY: =3D=3D21570=3D=3D definitely lost: 0 bytes in 0 blocks =3D=3D21570=3D=3D indirectly lost: 0 bytes in 0 blocks =3D=3D21570=3D=3D possibly lost: 0 bytes in 0 blocks =3D=3D21570=3D=3D still reachable: 0 bytes in 0 blocks =3D=3D21570=3D=3D suppressed: 4,096 bytes in 1 blocks =3D=3D21570=3D=3D=20 =3D=3D21570=3D=3D ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 fr= om 0) --21570--=20 --21570-- used_suppression: 1 MEMCHECK-LIBC-REACHABLE-1 /usr/local/libexec/valgrind/default.supp:595 suppressed: 4,096 bytes in 1 blocks =3D=3D21570=3D=3D=20 =3D=3D21570=3D=3D ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 fr= om 0) The suppression in question is used for an allocation that happens in libc: { MEMCHECK-LIBC-REACHABLE-1 Memcheck:Leak match-leak-kinds: reachable fun:malloc obj:*/lib*/libc.so.7 obj:*/lib*/libc.so.7 obj:*/lib*/libc.so.7 fun:vfprintf_l } Other than that, valgrind doesn't report any leaks. Although you tested on 14.1, I strongly suspect that it's the same false positive there. --=20 You are receiving this mail because: You are the assignee for the bug.=