dnsmasq: bump to version 2.73
PATCH 1/1 dnsmasq: bump to version 2.73
--- package/dnsmasq/dnsmasq.hash | 2 +- package/dnsmasq/dnsmasq.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/dnsmasq/dnsmasq.hash +1 -1
@@ -1,2 +1,2 @@ # Locally calculated after checking pgp signature -sha256 7d0bd23f5d74b3a6b26a75d5ffcf9db81d461b47cbe578cb65a83a98008600b1 dnsmasq-2.72.tar.xz +sha256 0bff81103e53fcab3a3c4d0fd6df1882f9446dca4fa74ff8270e1d2ab872d8f6 dnsmasq-2.73.tar.xz
package/dnsmasq/dnsmasq.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -DNSMASQ_VERSION = 2.72 +DNSMASQ_VERSION = 2.73 DNSMASQ_SOURCE = dnsmasq-$(DNSMASQ_VERSION).tar.xz DNSMASQ_SITE = http://thekelleys.org.uk/dnsmasq DNSMASQ_MAKE_ENV = $(TARGET_MAKE_ENV) CC="$(TARGET_CC)"
Signature · 1 line
2.3.6
Thomas Petazzoni
AppliedPATCH 1/1 dnsmasq: bump to version 2.73
Dear Gustavo Zacarias,
Quoted 5 lines · Gustavo Zacarias
Signed-off-by Gustavo Zacarias <[email protected]>--- package/dnsmasq/dnsmasq.hash | 2 +- package/dnsmasq/dnsmasq.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Applied, thanks.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 dnsmasq: bump to version 2.73
In reply to Gustavo ZacariasGustavo, All,
Quoted 9 lines · Gustavo Zacarias
Signed-off-by Gustavo Zacarias <[email protected]>--- package/dnsmasq/dnsmasq.hash | 2 +- package/dnsmasq/dnsmasq.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/dnsmasq/dnsmasq.mk line 7
Quoted 5 lines
package/dnsmasq/dnsmasq.mk +1
-1@@ -4,7 +4,7 @@ # ################################################################################ -DNSMASQ_VERSION = 2.72 +DNSMASQ_VERSION = 2.73
Tonight I was trying to use dnsmasq tonight for the first time for DNS and DHCP functionality. I'm unable to successfully start the application as it segs fault. After some debugging with strace turns out with the new version (2.73) of dnsmasq requires /tmp/resolv.conf to exist (actually /etc/resolv.conf since it sim links to /tmp/resolv.conf) even if you have the 'no-resolv' option specified in the config file. Below is the output from strace:
lstat64("/etc", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 lstat64("/etc/resolv.conf", {st_mode=S_IFLNK|0777, st_size=18, ...}) = 0 readlink("/etc/resolv.conf", "../tmp/resolv.conf", 4095) = 18 lstat64("/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=100, ...}) = 0 lstat64("/tmp/resolv.conf", 0xbea996f8) = -1 ENOENT (No such file or directory) --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0x4b5d0} --- +++ killed by SIGSEGV +++
Segmentation fault
I've verified if, 1) I revert this commit everything works or 2) if I add a touch to /tmp/resolv.conf to the S80dnsmasq startup script before invoking dnsmasq.
How do we want to address this issue? Is option 2 preferable?
Currently I'm not finding anything helpful on resolving this issue but it does appear there is some traffic on the mailing list for dnsmasq:
https://www.mail-archive.com/dnsmasq-discuss at lists.thekelleys.org.uk/msg09635.html
Thanks,
-Ryan
PATCH 1/1 dnsmasq: bump to version 2.73
Quoted 21 lines · Ryan Barnett
Tonight I was trying to use dnsmasq tonight for the first time for DNS and DHCP functionality. I'm unable to successfully start the application as it segs fault. After some debugging with strace turns out with the new version (2.73) of dnsmasq requires
/tmp/resolv.confto exist (actually/etc/resolv.confsince it sim links to/tmp/resolv.conf) even if you have the 'no-resolv' option specified in the config file. Below is the output from strace:
lstat64("/etc", {st_mode=S_IFDIR|0755, st_size=4096, ...})= 0lstat64("/etc/resolv.conf", {st_mode=S_IFLNK|0777, st_size=18, ...})= 0readlink("/etc/resolv.conf", "../tmp/resolv.conf", 4095)= 18lstat64("/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=100, ...})= 0lstat64("/tmp/resolv.conf", 0xbea996f8)= -1 ENOENT (No such file or directory)killed by SIGSEGV +++ renamed from SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0x4b5d0} --- +0
-0Segmentation fault
I've verified if, 1) I revert this commit everything works or 2) if I add a touch to
/tmp/resolv.confto the S80dnsmasq startup script before invoking dnsmasq.
Quoted 6 lines
How do we want to address this issue? Is option 2 preferable?
Currently I'm not finding anything helpful on resolving this issue but it does appear there is some traffic on the mailing list for dnsmasq:
https://www.mail-archive.com/dnsmasq-discuss at lists.thekelleys.org.uk/msg09635.html
Hi Ryan.
Wait for the 2.74 release (rc1 was recently released) that fixes this issue? Or backport the fix (probably 362c9303).
Regards.