From: Etienne Champetier <champetier.etienne@gmail.com>
To: Jonathan Foulkes <jf@jonathanfoulkes.com>
Cc: Sebastian Moeller <moeller0@gmx.de>,
cerowrt-devel@lists.bufferbloat.net,
Y via Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] New OpenWrt release fixing several dnsmasq CVEs
Date: Sat, 23 Jan 2021 15:04:53 -0500 [thread overview]
Message-ID: <CAOdf3grRcjddaA3B07Oze71GCQUw3kozrN7V-qC+iVa3a8yMig@mail.gmail.com> (raw)
In-Reply-To: <D61BE9D1-4E1C-4D67-BAD7-C34FC2AC4CA7@jonathanfoulkes.com>
Hi Jonathan,
Le sam. 23 janv. 2021 à 11:29, Jonathan Foulkes
<jf@jonathanfoulkes.com> a écrit :
>
> Hi Seb, someone did just that and even better, compared two builds with the dnsmasq being the only variable, and did not see any differences:
> https://forum.openwrt.org/t/security-advisory-2021-01-19-1-dnsmasq-multiple-vulnerabilities/85903/85
>
> From other comments, looks like they found the bug and are testing the fix.
> https://git.openwrt.org/?p=openwrt/staging/ldir.git;a=commitdiff;h=9a18346676850646764072ffcfd32ad9396d95c3
>
> Jonathan
>
> > On Jan 22, 2021, at 4:40 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
> >
> > Could you try to run top or htop and look at the CPU load? I could imagine that the fixes dnsmasq might have some CPU spikes that simply leave not enough cycles for the traffic shaper?
Is it possible you had a tab open on the Luci status page ?
In my experience if you don't have uhttpd-mod-ubus (and maybe
uhttpd-mod-lua) load average just keep climbing when you are looking
at this page.
https://bugs.openwrt.org/index.php?do=details&task_id=2613
Best
Etienne
prev parent reply other threads:[~2021-01-23 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 23:20 [Bloat] " Toke Høiland-Jørgensen
2021-01-22 19:33 ` Jonathan Foulkes
2021-01-22 21:15 ` Toke Høiland-Jørgensen
2021-01-22 21:25 ` Jonathan Foulkes
2021-01-22 21:27 ` Daniel Sterling
2021-01-22 21:40 ` Toke Høiland-Jørgensen
2021-01-22 21:40 ` Sebastian Moeller
2021-01-23 16:29 ` Jonathan Foulkes
2021-01-23 16:33 ` Daniel Sterling
2021-01-23 20:04 ` Etienne Champetier [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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOdf3grRcjddaA3B07Oze71GCQUw3kozrN7V-qC+iVa3a8yMig@mail.gmail.com \
--to=champetier.etienne@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=jf@jonathanfoulkes.com \
--cc=moeller0@gmx.de \
/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