RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1670043 - glibc: libresolv should use IP_RECVERR/IPV6_RECVERR to avoid long timeouts [rhel-8]
Summary: glibc: libresolv should use IP_RECVERR/IPV6_RECVERR to avoid long timeouts [r...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: glibc
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: Patsy Griffin
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On: 1670028
Blocks: 1670041 1684559
TreeView+ depends on / blocked
 
Reported: 2019-01-28 13:34 UTC by Florian Weimer
Modified: 2023-07-18 14:30 UTC (History)
7 users (show)

Fixed In Version: glibc-2.28-63.el8
Doc Type: No Doc Update
Doc Text:
Clone Of: 1670028
Environment:
Last Closed: 2019-11-05 21:29:04 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3513 0 None None None 2019-11-05 21:29:24 UTC
Sourceware 24047 0 P2 RESOLVED libresolv should use IP_RECVERR/IPV6_RECVERR to avoid long timeouts 2020-11-26 20:12:31 UTC

Description Florian Weimer 2019-01-28 13:34:04 UTC
+++ This bug was initially created as a clone of Bug #1670028 +++

The Linux kernel does not forward certain ICMP errors to userspace unless IP_RECVERR/IPV6_RECVERR is specified.  We should use this socket option in the DNS stub resolver, as suggested in the upstream bug.

Comment 3 Florian Weimer 2019-06-04 14:31:50 UTC
Upstream commit:

commit 08504de71813ddbd447bfbca4a325cbe8ce8bcda
Author: Florian Weimer <fweimer>
Date:   Tue Mar 12 11:40:47 2019 +0100

    resolv: Enable full ICMP errors for UDP DNS sockets [BZ #24047]
    
    The Linux kernel suppresses some ICMP error messages by default for
    UDP sockets.  This commit enables full ICMP error reporting,
    hopefully resulting in faster failover to working name servers.

Hurd-specific follow-on fix (optional):

commit 043440e761d395e1f507d9faa6e82b3fe4536c3f
Author: Florian Weimer <fweimer>
Date:   Wed Mar 13 14:58:58 2019 +0100

    hurd: Add no-op version of __res_enable_icmp [BZ #24047]
    
    Mach does not support IP_RECVERR, so replace this function with a
    stub in a sysdeps override for Hurd.
    
    This fixes commit 08504de71813ddbd447bfbca4a325cbe8ce8bcda
    ("resolv: Enable full ICMP errors for UDP DNS sockets [BZ #24047]").

For verification, I think it is sufficient to check that strace shows the additional setsockopt call.

Comment 5 Sergey Kolosov 2019-09-09 07:05:54 UTC
Verified with strace

Comment 7 errata-xmlrpc 2019-11-05 21:29:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3513


Note You need to log in before you can comment on or make changes to this bug.