Date: Fri, 06 Dec 2024 13:34:43 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 279901] glibc-2.39-2 and above on the host segfault Message-ID: <bug-279901-27103-jwoxUH5Iis@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-279901-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-279901-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279901 Adhemerval Zanella <zatrazz@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zatrazz@gmail.com --- Comment #19 from Adhemerval Zanella <zatrazz@gmail.com> --- I am trying to reproduce it with a different hypervisor/emulation (in this = case qemu/kvm) with a Ryzen 9 5900x Zen3 core but both AlmaLinux 10 Kitten (glibc 2.39) and debian sid (glibc 2.40) boots and works without any issue. And I also verified on debian sid the selected memcpy/memmove is indeed the= one that optimized with glibc change (__memcpy_avx_unaligned_erms). I even trie= d to run glibc memcpy/memmove tests in this VM, where they stress a lot of diffe= rent sizes and alignments for different memcpy/memmove implementations. Also, my daily workstation (Ryzen 9 5900x) the uses a recent glibc that also contains this issue and I haven't see any memcpy/memmove related issue. So I am not sure if this is a glibc issue. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279901-27103-jwoxUH5Iis>