From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Pending patches for upcoming Core Update 154 Date: Wed, 27 Jan 2021 20:13:36 +0100 Message-ID: <6e4dc725-5891-4465-f7fb-182d90b466ee@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1736772559275542626==" List-Id: --===============1736772559275542626== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Peter, On 27/01/2021 20:04, Peter M=C3=BCller wrote: > Hello development folks, > > Man proposes, God disposes... *sigh* > > Is anyone aware about current kernel in next being un-compilable or am I bu= mping into some > personal side-effects again? I started a build about two hours ago after a git pull from next and Linux bu= ilt without any problems on my system. I was updating sudo and arping but after starting I saw that you are also wor= king on sudo so I will just send in the patch for arping. Regards, Adolf. >> linux (4.14.212) = = KCFG=3D[ 3:4= 8 ][ FAIL ] >> >> 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 s= ection .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 s= ection .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 sectio= n .text >> CC [M] fs/xfs/xfs_rtalloc.o >> fs/xfs/.tmp_xfs_dquot.o: warning: objtool: missing symbol for section= .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 > Unfortunately, ~/devel/ipfire-2.x/log/_build.ipfire.log does not contain fu= rther information regarding > the problem. Having had some issues with a too old kernel on my workstation= , this should now be fine again: > >> 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 2021 = (9898712) x86_64 x86_64 x86_64 GNU/Linux > Am I missing something? If yes, could somebody please enlighten my tired br= ain? :-) > > Thanks, and best regards, > Peter M=C3=BCller > >> Hello *, >> >> to avoid redundancies: I am currently working on Postfix 3.5.9 and (more i= mportant) 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. >> >> There might be some minor stuff (USB/PCI database files, etc.) to do as we= ll, but I have >> not checked that, yet. :-) >> >> Thanks, and best regards, >> Peter M=C3=BCller >> --===============1736772559275542626==--