[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#794336: marked as done ([e]glibc breaks res_init() functionality)

Your message dated Sun, 26 Nov 2017 23:51:15 +0100
with message-id <20171126225115.ak7gnwxeblmzxn4m@aurel32.net>
and subject line Re: Bug#794336: [e]glibc breaks res_init() functionality
has caused the Debian Bug report #794336,
regarding [e]glibc breaks res_init() functionality
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
794336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794336
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
package: glibc

I don't know whether this is still relevant or not, as I know Debian has
switched back to the original glibc, which does not contain this bug, but...

A patch to Debian's glibc, introduced here:
https://lists.debian.org/debian-glibc/2006/06/msg00154.html contains a
bug, which breaks the functionality of res_init().

res_init() is supposed to initalize the _res struct, and then allow for
modifications to the _res struct by the user, before resolving something
using res_query().

The introduction of the 'last_mtime' stat struct was used to determine
whether or not the _res struct had to be re-initalized, as the last
modification time of /etc/resolv.conf had changed. However, res_query()
uses __res_maybe_init() to determine whether or not to reset _res, but
res_init() does not set statbuf. So, calling res_init() effectively does
nothing, since all the changes will be overwritten by the first call to
res_query(), because res_query() runs __res_maybe_init().


Ubuntu report here, for reference:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1432378/comments/4


Thanks!

(Apologies if this has done through twice. I haven't used Debian's bug tracking for awhile.)

-- 
-- Joshua Rogers <https://internot.info/>

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Version: 2.26-0experimental0

On 2015-08-02 01:16, Joshua Rogers wrote:
> package: glibc
> 
> I don't know whether this is still relevant or not, as I know Debian has
> switched back to the original glibc, which does not contain this bug, but...
> 
> A patch to Debian's glibc, introduced here:
> https://lists.debian.org/debian-glibc/2006/06/msg00154.html contains a
> bug, which breaks the functionality of res_init().
> 
> res_init() is supposed to initalize the _res struct, and then allow for
> modifications to the _res struct by the user, before resolving something
> using res_query().
> 
> The introduction of the 'last_mtime' stat struct was used to determine
> whether or not the _res struct had to be re-initalized, as the last
> modification time of /etc/resolv.conf had changed. However, res_query()
> uses __res_maybe_init() to determine whether or not to reset _res, but
> res_init() does not set statbuf. So, calling res_init() effectively does
> nothing, since all the changes will be overwritten by the first call to
> res_query(), because res_query() runs __res_maybe_init().
> 
> 
> Ubuntu report here, for reference:
> https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1432378/comments/4

This bug has been fixed in glibc 2.26, as way to reload /etc/resolv.conf
rewritten and merged differently upstream. Marking the bug as closed for
this version.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: