Bug 1458542 - kernel: ICMP rate limiting is too aggressive on loopback
Summary: kernel: ICMP rate limiting is too aggressive on loopback
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1458586 (view as bug list)
Depends On:
Blocks: 1461282
TreeView+ depends on / blocked
 
Reported: 2017-06-04 07:16 UTC by Florian Weimer
Modified: 2026-07-24 14:54 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
: 1461282 (view as bug list)
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
localhost-icmp.c (1.63 KB, text/x-csrc)
2017-06-04 07:16 UTC, Florian Weimer
no flags Details

Description Florian Weimer 2017-06-04 07:16:32 UTC
Created attachment 1284717 [details]
localhost-icmp.c

Description of problem:

Aggressive ICMP rate limiting on the loopback interface causes test suite failures.

Version-Release number of selected component (if applicable):

kernel-4.11.3-200.fc25.x86_64

How reproducible:

Always.

Steps to Reproduce:
1. Compile localhost-icmp.c.
2. Run ./localhost-icmp

Actual results:

Test runs into a timeout:

localhost-icmp: iteration 50: no ICMP message (poll timeout)

Expected results:

Test completes within a few milliseconds.

Additional info:

https://sourceware.org/ml/libc-alpha/2017-06/msg00167.html
http://marc.info/?l=linux-netdev&m=149656032817085

Comment 1 Florian Weimer 2017-06-04 15:28:16 UTC
*** Bug 1458586 has been marked as a duplicate of this bug. ***

Comment 2 Charles Haithcock 2026-07-24 14:54:17 UTC
This report has not received an update in over 90 days. If this issue is still relevant to you, please do not hesitate to update this report with any relevant details on recent investigative steps or changes and we will absolutely work to understand how to best move forward. Otherwise, this bug report will need to be closed in 30 days. No worries, however; should you need still assistance after the report is closed, please do not hesitate to create a new bug report referencing this report and with any new details on the matter. 

NOTE: This is an automated mass update.


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