about summary refs log tree commit diff
path: root/resolv/resolv_context.c
Commit message (Collapse)AuthorAgeFilesLines
* resolv: Automatically reload a changed /etc/resolv.conf file [BZ #984]Florian Weimer2017-07-031-15/+38
| | | | | | | | | | This commit enhances the stub resolver to reload the configuration in the per-thread _res object if the /etc/resolv.conf file has changed. The resolver checks whether the application has modified _res and will not overwrite the _res object in that case. The struct resolv_context mechanism is used to check the configuration file only once per name lookup.
* resolv: Introduce struct resolv_conf with extended resolver stateFlorian Weimer2017-07-031-5/+33
| | | | | | | | | | | | This change provides additional resolver configuration state which is not exposed through the _res ABI. It reuses the existing initstamp field in the supposedly-private part of _res. Some effort is undertaken to avoid memory safety issues introduced by applications which directly patch the _res object. With this commit, only the initstamp field is moved into struct resolv_conf. Additional members will be added later, eventually migrating the entire resolver configuration.
* resolv: Introduce struct resolv_context [BZ #21668]Florian Weimer2017-07-031-0/+201
struct resolv_context objects provide a temporary resolver context which does not change during a name lookup operation. Only when the outmost context is created, the stub resolver configuration is verified to be current (at present, only against previous res_init calls). Subsequent attempts to obtain the context will reuse the result of the initial verification operation. struct resolv_context can also be extended in the future to store data which needs to be deallocated during thread cancellation.