This bug was fixed in the package dnsmasq - 2.71-1
---
dnsmasq (2.71-1) unstable; urgency=low
* New upstream.
* Fix 100% CPU-usage bug when dnsmasq started with cachesize
set to zero. (LP: #1314697)
-- Simon Kelley Fri, 16 May 2014 20:17:10 +
** Changed i
** Branch linked: lp:ubuntu/utopic-proposed/dnsmasq
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314697
Title:
DNS resolution no longer works; dnsmasq uses 100% CPU
To manage notifications about
** Branch linked: lp:debian/dnsmasq
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314697
Title:
DNS resolution no longer works; dnsmasq uses 100% CPU
To manage notifications about this bug go to:
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1314697
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
On 08/05/14 22:18, James Hunt wrote:
> A bit of debugging shows that the culprit is blockdata_expand() which is
> being called via blockdata_init(). The issue seems to be that
> blockdata_expand() is passed a parameter of zero. That function then
> mallocs zero bytes (successfully seemingly), the p
A bit of debugging shows that the culprit is blockdata_expand() which is
being called via blockdata_init(). The issue seems to be that
blockdata_expand() is passed a parameter of zero. That function then
mallocs zero bytes (successfully seemingly), the proceeds to overwrite
data before the returned
BTW - the problem is recreatable for me every time simply by spinning up
a utopic kvm instance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314697
Title:
DNS resolution no longer works; dnsmasq u
Annoyingly, I still can't reproduce this on the systems I have
available. On a system where the problem occurs, can it be reproduced
when dnsmasq is started standalone with the same command-line
parameters? The idea situation would be to get the bug to show up in a
dnsmasq instance running under gd
Updated description since problem is unrelated to upgrade - it just
occurs with the version of dnsmasq currently in utopic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314697
Title:
DNS resolutio
