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 1334775 - backport upstream ping change unmasking signals
Summary: backport upstream ping change unmasking signals
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iputils
Version: 6.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: Tomas Dolezal
URL:
Whiteboard:
Depends On:
Blocks: 1269194 1356047 1359260
TreeView+ depends on / blocked
 
Reported: 2016-05-10 13:56 UTC by Karl Hastings
Modified: 2023-03-24 13:41 UTC (History)
5 users (show)

Fixed In Version: iputils-20071127-24.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 09:29:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
reproducer (494 bytes, text/plain)
2016-05-10 14:02 UTC, Karl Hastings
no flags Details
reporoducer (731 bytes, text/x-csrc)
2016-11-29 17:18 UTC, Tomas Dolezal
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0604 0 normal SHIPPED_LIVE iputils bug fix update 2017-03-21 12:26:37 UTC

Description Karl Hastings 2016-05-10 13:56:46 UTC
Description of problem:
'ping' and 'arping' in RHEL6 iputils does not unmask signals.  This can cause issues when ping is called from a parent process that has masked signals.

Upstream has fixed this with the following commit:
http://www.linux-ipv6.org/gitweb/gitweb.cgi?p=gitroot/iputils.git;a=blobdiff;f=ping_common.c;h=3d03bb60fef22e312305a37430f1edf9bcb5af76;hp=eaedca8f2ac97379947abe8383a414d884bd3f34;hb=810dd7fc2aed5c81382de2c92d3533fc440c8868;hpb=612b3af5ceca5accdb4b67f33314b188c2c9f628

Customer requests this change be backported to RHEL6.

Version-Release number of selected component (if applicable):
iputils-20071127-21.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. call `ping -c 6 -w 1 169.254.111.111` from a process with signals masked
2.
3.

Actual results:
ping continues sending packets forever, never receiving the SIGALRM ( '-w 1' sends a SIGALRM after 1 second).

Expected results:
ping should exit after 1 second

Additional info:

Comment 2 Karl Hastings 2016-05-10 14:00:30 UTC
This was fixed for 'arping' in Fedora 20 via https://bugzilla.redhat.com/show_bug.cgi?id=1085971

But upstream fixed it in a different way.

I'm attaching a small c program that demonstrates the problem.  The code is based on the reproducer in BZ#1085971

Comment 3 Karl Hastings 2016-05-10 14:02:13 UTC
Created attachment 1155765 [details]
reproducer

Comment 17 errata-xmlrpc 2017-03-21 09:29:34 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://rhn.redhat.com/errata/RHBA-2017-0604.html


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