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 1387542 - arping -c <n> does not exit when the device is deleted
Summary: arping -c <n> does not exit when the device is deleted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iputils
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: Robin Hack
URL:
Whiteboard:
Depends On: 1225122
Blocks: 1380361
TreeView+ depends on / blocked
 
Reported: 2016-10-21 08:44 UTC by Attila Fazekas
Modified: 2017-08-01 20:47 UTC (History)
6 users (show)

Fixed In Version: iputils-20160308-9.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1225122
Environment:
Last Closed: 2017-08-01 20:47:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1987 0 normal SHIPPED_LIVE iputils bug fix update 2017-08-01 18:32:29 UTC

Description Attila Fazekas 2016-10-21 08:44:48 UTC
iputils-20160308-8.el7.x86_64 also has the same miss behavior .


+++ This bug was initially created as a clone of Bug #1225122 +++

Description of problem:
arping with '-c' option tries to ping forever when a parallel operation  deletes the -I <device>.

Version-Release number of selected component (if applicable):
iputils-20140519-4.fc21.x86_64

How reproducible:
always

Steps to Reproduce:
$ ip tuntap add mode tap dev test; ifconfig test 10.4.4.1/24; ip link set up dev test; (sleep 1; ip link delete test) & arping -U -I test -c 13 10.4.4.1
[1] 7258
ARPING 10.4.4.1 from 10.4.4.1 test
arping: recvfrom: Network is down

# It does not returns the prompt, blocked in arping.

Actual results:
arping never exit, this causes neutron-lbaas service does not operates properly.

Expected results:
The arping with -c option (without -w) MUST exit after the number (-c) of tries.

The failed attempts should not be counted as sent ARP at the end.

The el7 version of arping behaves as it expected (iputils-20121221-6.el7.x86_64).
#  ip tuntap add mode tap dev test; ifconfig test 10.4.4.1/24; ip link set up dev test; (sleep 1; ip link delete test) & arping -U -I test -c 13 10.4.4.1
[1] 18570
ARPING 10.4.4.1 from 10.4.4.1 test
arping: recvfrom: Network is down
Sent 2 probes (2 broadcast(s))
Received 0 response(s)
[1]+  Done                    ( sleep 1; ip link delete test )

# # I got back the prompt after ~ 13 arping time, but actually it did only 2 successful sent attempt, before the link got deleted.

 
Additional info:
According to strace arping does the following in an infinite loop. 

recvfrom(3, 0x7ffdeafe47b0, 4096, 0, 0x7ffdeafe4730, 0x7ffdeafe4620) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
--- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} ---
clock_gettime(CLOCK_MONOTONIC, {21930, 694909708}) = 0
clock_gettime(CLOCK_MONOTONIC, {21930, 694939330}) = 0
sendto(3, "\0\1\10\0\6\4\0\1\316.Dd*\273\n\4\4\1\377\377\377\377\377\377\n\4\4\1", 28, 0, {sa_family=AF_PACKET, proto=0x806, if14, pkttype=PACKET_HOST, addr(6)={1, ffffffffffff}, 20) = -1 ENXIO (No such device or address)
alarm(1)                                = 0
rt_sigreturn({mask=[]})                 = 45
recvfrom(3, 0x7ffdeafe47b0, 4096, 0, 0x7ffdeafe4730, 0x7ffdeafe4620) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)

--- Additional comment from Attila Fazekas on 2015-06-03 09:59:58 EDT ---

The issue also happens with f22 iputils-20140519-4.fc22.x86_64.

iputils-20121221-4.fc20.x86_64 is OK.

--- Additional comment from Fedora End Of Life on 2015-11-04 06:35:59 EST ---

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

--- Additional comment from Fedora End Of Life on 2015-12-02 08:00:19 EST ---

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--- Additional comment from Attila Fazekas on 2016-10-21 04:25:55 EDT ---

I have the same issue with iputils-20160308-3.fc24.x86_64 .

Comment 2 Jan Synacek 2017-02-23 12:02:39 UTC
https://github.com/iputils/iputils/pull/79

Comment 7 errata-xmlrpc 2017-08-01 20:47:16 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/RHBA-2017:1987


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