[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bddc66e5-a8bb-b60e-53b3-fd56be8beb37@wwsnet.net>
Date: Sat, 8 Oct 2022 01:53:29 +0200
From: Jo-Philipp Wich <jo@...n.io>
To: Rich Felker <dalias@...c.org>,
Uwe Kleine-König <uwe+openwrt@...ine-koenig.org>
Cc: openwrt-devel@...ts.openwrt.org, musl@...ts.openwall.com
Subject: Re: nslookup failures with coarse CLOCK_MONOTONIC
Hi,
> [...]
> Which implementation of nslookup is this? Busybox? It would probably
> be useful to hear thoughts on it from their side.
assuming the OP is using standard OpenWrt nslookup, it is the "big" busybox
nslookup implementation, which is using the res_*() api and name lookup logic
borrowed from musl libc instead of the original "small" version fiddling with
the `_res` state directly (and being broken on musl libc due to that).
The proper course of action here is likely adapting the solution in
6c858d6fd4df8b5498ef2cae66c8f3c3eff1587b and porting it to the busybox "big"
nslookup code itself.
I agree that musl libc itself cannot do much more to ensure uniqueness of the
IDs generated by res_mkquery() and that it should be solved in the application
code itself in this case.
Regards,
Jo
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
