public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Pending patches for upcoming Core Update 154
Date: Wed, 27 Jan 2021 21:05:11 +0100	[thread overview]
Message-ID: <fde45600-ed48-ad85-86f5-8f25ab50d3ec@ipfire.org> (raw)
In-Reply-To: <cdc3f8e1-5da1-c202-6c6e-35648d84b3e0@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 4398 bytes --]

Hi there Peter,

On 27/01/2021 20:58, Peter Müller wrote:
> Good evening Adolf,
> 
> thanks for your reply.
> 
> The problem is at my end, then. Would you mind working on sudo anyways, so we definitely have
> a patch ready for Core Update 154? I would skip it then - but are of course willing to review
> your patch and/or help, if any help is needed (and I got my environment ready until then). :-)

No problem. I had left the build going anyway as arping was also being built and it has just finished with no issues and no change to the rootfile. I will send in the patch for review.

Regards,
Adolf
> 
> Thanks, and best regards,
> Peter Müller
> 
> 
>> Hi Peter,
>>
>>
>> On 27/01/2021 20:04, Peter Müller wrote:
>>> Hello development folks,
>>>
>>> Man proposes, God disposes... *sigh*
>>>
>>> Is anyone aware about current kernel in next being un-compilable or am I bumping into some
>>> personal side-effects again?
>>
>> I started a build about two hours ago after a git pull from next and Linux built without any problems on my system.
>>
>> I was updating sudo and arping but after starting I saw that you are also working on sudo so I will just send in the patch for arping.
>>
>> Regards,
>>
>> Adolf.
>>
>>>> linux (4.14.212)                                                                                                                                                                                                    KCFG=[     3:48 ][ 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 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 section .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 further 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 brain? :-)
>>>
>>> Thanks, and best regards,
>>> Peter Müller
>>>
>>>> Hello *,
>>>>
>>>> to avoid redundancies: I am currently working on Postfix 3.5.9 and (more 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.
>>>>
>>>> There might be some minor stuff (USB/PCI database files, etc.) to do as well, but I have
>>>> not checked that, yet. :-)
>>>>
>>>> Thanks, and best regards,
>>>> Peter Müller
>>>>

  reply	other threads:[~2021-01-27 20:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 17:15 Peter Müller
2021-01-27 19:04 ` Peter Müller
2021-01-27 19:13   ` Adolf Belka
2021-01-27 19:58     ` Peter Müller
2021-01-27 20:05       ` Adolf Belka [this message]
2021-01-28 20:20   ` Peter Müller
2021-01-30 16:29     ` Michael Tremer
2021-01-30 17:26       ` Peter Müller
2021-02-01 11:17         ` Michael Tremer
2021-01-30 13:00 ` Matthias Fischer
2021-01-30 13:08   ` Peter Müller
2021-01-30 13:51     ` Adolf Belka
2021-01-30 16:52       ` Adolf Belka
     [not found] <AC2550F9-7FCE-4533-90BF-B8E46F825D8E@gmail.com>
2021-02-05  8:32 ` Adolf Belka
2021-02-05 11:10 ` Michael Tremer
     [not found] <26ED65B8-154A-4476-B9E6-7DCD58078E0C@gmail.com>
2021-02-05 11:10 ` Michael Tremer
2021-02-05 11:38   ` Adolf Belka
2021-02-05 16:19     ` Michael Tremer
2021-02-05 17:31       ` Adolf Belka
2021-02-05 17:46         ` Michael Tremer
2021-02-05 17:59           ` Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fde45600-ed48-ad85-86f5-8f25ab50d3ec@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox