Date: Mon, 29 Oct 2018 19:44:11 +0000 From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 232387] head -r339076: system crash in vnet_epair_init during kern_jail_set in a kyua test on powerpc64 Message-ID: <bug-232387-25139-MQHsfrQUSA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-232387-25139@https.bugs.freebsd.org/bugzilla/> References: <bug-232387-25139@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=3D232387 --- Comment #12 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #10) It turns out that my amd64 kernel builds are like the devel/powerpc64-xtoolchain-gcc ones in that instead of SHN_ABS it has a normal st_shndx value: ( these are looking at /boot/kernel/kernel ) entry: 16765 st_name: __start_set_vnet st_value: 0xffffffff824dc200 st_size: 0 st_info: STT_NOTYPE STB_GLOBAL st_shndx: 50 This might suggest powerpc64's kernel having incomplete coverage for handling such things? For the amd64 context, that 50 is: entry: 50 sh_name: set_vnet sh_type: SHT_PROGBITS sh_flags: SHF_WRITE|SHF_ALLOC sh_addr: 0xffffffff824dc200 sh_offset: 36553216 sh_size: 220872 sh_link: 0 sh_info: 0 sh_addralign: 16 sh_entsize: 0 A constrasting devel/powerpc64-xtoolchain-gcc based kernel has entries (note the set_vnet sh_flags differences vs. amd64): ( these are also looking at /boot/kernel/kernel ) entry: 40 sh_name: set_vnet sh_type: SHT_PROGBITS sh_flags:=20 sh_addr: 0x1223800 sh_offset: 18036736 sh_size: 212656 sh_link: 0 sh_info: 0 sh_addralign: 8 sh_entsize: 0 and for __start_set_vnet : entry: 1490 st_name: __start_set_vnet st_value: 0x1223800 st_size: 0 st_info: STT_NOTYPE STB_GLOBAL st_shndx: 40 --=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-232387-25139-MQHsfrQUSA>