res_state and res_init definition order in resolv.c
Kenneth.Sorensen at spectralink.com
Fri Aug 9 11:12:18 UTC 2013
While you are looking into this issue will you please take my suggested patches into consideration?
This one specifically addresses the issue described below.
This one makes res_init() thread safe.
Please see my explanation in the mail.
Thank you for your time.
From: uclibc-bounces at uclibc.org <uclibc-bounces at uclibc.org> on behalf of Bernhard Reutner-Fischer <rep.dot.nop at gmail.com>
Sent: Monday, July 15, 2013 11:41
To: Eugene Rudoy; uclibc at uclibc.org
Subject: Re: res_state and res_init definition order in resolv.c
On 13 July 2013 13:17:25 Eugene Rudoy <gene.devel at gmail.com> wrote:
> Hi all,
> could someone who is familiar with resolv.c and understands all its res_init
> related tricks please comment the following two commits:
>  "resolv.c: add support for per thread
> the comment it contains "This needs to be after the use of _res in
> res_init, above."
>  "inet/resolv: add res_ninit and
> moves res_init after the definition of _res/__resp without modifying the
> comment from  and without explaining whether it still applies or not.
> The question arises in the context of understanding whether the patch
> provided in OpenWRT ticket 11929 <https://dev.openwrt.org/ticket/11929> is
> a correct one and why it works for some people and doesn't work for the
> other ones.
I will have a look.
Sent with AquaMail for Android
uClibc mailing list
uClibc at uclibc.org
More information about the uClibc