From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: dhcpcd 8.1.1 is out
Date: Thu, 17 Oct 2019 13:52:47 +0200 [thread overview]
Message-ID: <57f91097-0513-7463-4132-cfcec3e6a6eb@ipfire.org> (raw)
In-Reply-To: <34872747-2AE6-45D9-A637-B5384F80E3B8@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]
On 17.10.2019 11:47, Michael Tremer wrote:
> Hi,
Hi - sorry, seen too late.
> Are we expecting that this will fix the crash?
Good question. I would says: yes, but you'll never know. Software is evil...
Besides, not everyone ran into this error. But it seems that both fixed
and dhcp addresses on red0 are affected in some way.
For now, Arne reverted 'next' back to 'dhcpcd 7.2.3'
(https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=refs/heads/next).
In the meantime, Roy Marples is working on SEGVs, (udp-)checksum
failures and core dumps with 8.x.x
(https://roy.marples.name/archives/dhcpcd-discuss/). Doesn't sound good,
but never happened here. I never saw that much noise on that list.
> Do we even have a ticket for that?
Not yet. Right now, discussion is taking place in the forum
(https://forum.ipfire.org/viewtopic.php?f=27&t=23455).
At the moment I'm running '8.1.1' on Core136/32bit and as with the other
8.x.x-versions do have no problems.
Best,
Matthias
> Best,
> -Michael
>
>> On 16 Oct 2019, at 17:21, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>
>> Hi,
>>
>> 'dhcpcd 8.1.1' is out.
>>
>> => https://roy.marples.name/archives/dhcpcd-discuss/0002641.html
>>
>> "dhcpcd-8.1.1 has been released with the following changes:
>>
>> * IPv6: Fix a potential crash when udevs marks an interface ready.
>> * Linux: compat shim added for setproctitle(3).
>> * arc4random: fixed UB in compat shim.
>> * DHCP: Fix fallout from dhcpcd-8.1.0 for checksum calculation.
>>
>> The last fix involved a lot a people, quite a few different fixes and
>> played havoc with gcc-9.2 but should now be resolved."
>>
>> I'm working on it.
>>
>> Best,
>> Matthias
>
>
prev parent reply other threads:[~2019-10-17 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 16:21 Matthias Fischer
2019-10-17 9:47 ` Michael Tremer
2019-10-17 11:52 ` Matthias Fischer [this message]
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=57f91097-0513-7463-4132-cfcec3e6a6eb@ipfire.org \
--to=matthias.fischer@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