mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jo-Philipp Wich <jo@mein.io>
To: "Rich Felker" <dalias@libc.org>,
	"Uwe Kleine-König" <uwe+openwrt@kleine-koenig.org>
Cc: openwrt-devel@lists.openwrt.org, musl@lists.openwall.com
Subject: Re: [musl] nslookup failures with coarse CLOCK_MONOTONIC
Date: Sat, 8 Oct 2022 01:53:29 +0200	[thread overview]
Message-ID: <bddc66e5-a8bb-b60e-53b3-fd56be8beb37@wwsnet.net> (raw)
In-Reply-To: <20221007232540.GC29905@brightrain.aerifal.cx>


[-- Attachment #1.1: Type: text/plain, Size: 826 bytes --]

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-10-07 23:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 23:04 Uwe Kleine-König
2022-10-07 23:25 ` Rich Felker
2022-10-07 23:53   ` Jo-Philipp Wich [this message]
2022-10-08  0:05     ` Rich Felker
2022-10-08  0:37   ` Uwe Kleine-König
2022-10-08  7:07     ` Markus Wichmann

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=bddc66e5-a8bb-b60e-53b3-fd56be8beb37@wwsnet.net \
    --to=jo@mein.io \
    --cc=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=uwe+openwrt@kleine-koenig.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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).