From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Pending patches for upcoming Core Update 154 Date: Mon, 01 Feb 2021 11:17:01 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3850366648232073447==" List-Id: --===============3850366648232073447== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, > On 30 Jan 2021, at 17:26, Peter M=C3=BCller wr= ote: >=20 > Hello Michael, >=20 > thank you for trying to reproduce this. >=20 > I am currently building current IPFire 2.x "next" with ccache deleted and w= ill report my findings/ > progress here. (binutils 2.36 turns out to break so much stuff that I am cu= rrently considering not > to send in a patch for it and wait for linux/hyperscan/... to adapt by them= selves. Hrmpf.) I do not see anything in the change log that sounds potentially dangerous and= would break things. It simply sounds like there has something gone wrong with your compiler cache= (it also caches linked objects, too). -Michael > Thanks, and best regards, > Peter M=C3=BCller >=20 >> Hi, >> I installed a virtual machine with OpenSuSE Leap and I am past the kernel = now with my build. >> Could you simply remove the ccache directory from your build environment a= nd run your build again? >> It does not seem to be the distribution. >> -Michael >>> On 28 Jan 2021, at 20:20, Peter M=C3=BCller = wrote: >>>=20 >>> Hello *, >>>=20 >>> to keep everyone updated: The root cause for this seems to be a quirk som= ewhere in the vicinity >>> of objtools (part of the binutils): >>>=20 >>>> arch/x86/crypto/sha512-mb/.tmp_sha512_mb_mgr_flush_avx2.o: warning: objt= ool: missing symbol for section .text >>>> CC [M] arch/x86/crypto/sha512-mb/sha512_mb_mgr_init_avx2.o >>>> AS [M] arch/x86/crypto/sha512-mb/sha512_mb_mgr_submit_avx2.o >>>> arch/x86/crypto/sha512-mb/.tmp_sha512_mb_mgr_submit_avx2.o: warning: obj= tool: missing symbol for section .text >>>> AS [M] arch/x86/crypto/sha512-mb/sha512_x4_avx2.o >>>> arch/x86/crypto/sha512-mb/.tmp_sha512_x4_avx2.o: warning: objtool: missi= ng symbol for section .text >>>> LD [M] arch/x86/crypto/sha512-mb/sha512-mb.o >>>> AS arch/x86/entry/entry_64.o >>>> arch/x86/entry/entry_64.S: Assembler messages: >>>> arch/x86/entry/entry_64.S:1642: Warning: no instruction mnemonic suffix = given and no register operands; using default for `sysret' >>>> AS arch/x86/entry/thunk_64.o >>>> arch/x86/entry/.tmp_thunk_64.o: warning: objtool: missing symbol table >>>> make[3]: *** [scripts/Makefile.build:427: arch/x86/entry/thunk_64.o] Err= or 1 >>>> make[2]: *** [scripts/Makefile.build:585: arch/x86/entry] Error 2 >>>> make[1]: *** [Makefile:1053: arch/x86] Error 2 >>>> make[1]: Leaving directory '/usr/src/linux-4.14.212' >>>> make: *** [linux:150: /usr/src/log/linux-4.14.212-ipfire] Error 2 >>>=20 >>> Alas, this is currently reproducible on OpenSuSE Leap 15.2 machines tryin= g to build an untouched >>> version of IPFire 2.x (both "next" and "master"). :-/ >>>=20 >>> Thanks, and best regards, >>> Peter M=C3=BCller >>>=20 >>>=20 >>>> Hello development folks, >>>>=20 >>>> Man proposes, God disposes... *sigh* >>>>=20 >>>> Is anyone aware about current kernel in next being un-compilable or am I= bumping into some >>>> personal side-effects again? >>>>=20 >>>>> linux (4.14.212) = = KCFG=3D[ = 3:48 ][ FAIL ] >>>>>=20 >>>>> CC [M] fs/xfs/xfs_inode_item.o >>>>> CC [M] fs/xfs/xfs_refcount_item.o >>>>> CC [M] fs/xfs/xfs_rmap_item.o >>>>> CC [M] fs/xfs/xfs_log_recover.o >>>>> CC [M] fs/xfs/xfs_trans_ail.o >>>>> CC [M] fs/xfs/xfs_trans_bmap.o >>>>> CC [M] fs/xfs/xfs_trans_buf.o >>>>> CC [M] fs/xfs/xfs_trans_extfree.o >>>>> CC [M] fs/xfs/xfs_trans_inode.o >>>>> CC [M] fs/xfs/xfs_trans_refcount.o >>>>> CC [M] fs/xfs/xfs_trans_rmap.o >>>>> CC [M] fs/xfs/xfs_dquot.o >>>>> CC [M] fs/xfs/xfs_dquot_item.o >>>>> fs/xfs/.tmp_xfs_trans_inode.o: warning: objtool: missing symbol for = section .text >>>>> CC [M] fs/xfs/xfs_trans_dquot.o >>>>> CC [M] fs/xfs/xfs_qm_syscalls.o >>>>> CC [M] fs/xfs/xfs_qm_bhv.o >>>>> fs/xfs/.tmp_xfs_trans_dquot.o: warning: objtool: missing symbol for = section .text >>>>> CC [M] fs/xfs/xfs_qm.o >>>>> CC [M] fs/xfs/xfs_quotaops.o >>>>> fs/xfs/.tmp_xfs_qm_bhv.o: warning: objtool: missing symbol for secti= on .text >>>>> CC [M] fs/xfs/xfs_rtalloc.o >>>>> fs/xfs/.tmp_xfs_dquot.o: warning: objtool: missing symbol for sectio= n .init.text >>>>> CC [M] fs/xfs/xfs_acl.o >>>>> CC [M] fs/xfs/xfs_sysctl.o >>>>> CC [M] fs/xfs/xfs_ioctl32.o >>>>> LD [M] fs/xfs/xfs.o >>>>> AR fs/built-in.o >>>>> make[1]: Leaving directory '/usr/src/linux-4.14.212' >>>>> make: *** [linux:149: /usr/src/log/linux-4.14.212-ipfire] Error 2 >>>>=20 >>>> Unfortunately, ~/devel/ipfire-2.x/log/_build.ipfire.log does not contain= further information regarding >>>> the problem. Having had some issues with a too old kernel on my workstat= ion, this should now be fine again: >>>>=20 >>>>> user(a)machine:~/devel/ipfire-2.x> uname -a >>>>> Linux machine 5.3.18-lp152.60-default #1 SMP Tue Jan 12 23:10:31 UTC 20= 21 (9898712) x86_64 x86_64 x86_64 GNU/Linux >>>>=20 >>>> Am I missing something? If yes, could somebody please enlighten my tired= brain? :-) >>>>=20 >>>> Thanks, and best regards, >>>> Peter M=C3=BCller >>>>=20 >>>>> Hello *, >>>>>=20 >>>>> to avoid redundancies: I am currently working on Postfix 3.5.9 and (mor= e important) sudo >>>>> 1.9.5p2 for upcoming Core Update 154. Both fix some security issues; I = am pretty sure you >>>>> have heard of CVE-2021-3156 affecting the latter by now. >>>>>=20 >>>>> There might be some minor stuff (USB/PCI database files, etc.) to do as= well, but I have >>>>> not checked that, yet. :-) >>>>>=20 >>>>> Thanks, and best regards, >>>>> Peter M=C3=BCller >>>>>=20 --===============3850366648232073447==--