Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

This bug was initially created as a copy of Bug #2192559

Description of problem:
When the netlink socket of a port (used for receiving link up/down events) has the ENOBUFS error due to the kernel sending too many messages at once, ptp4l floods the system log with "port 1: unexpected socket error" messages and is not able to recover from the error.

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

How reproducible:
always

Steps to Reproduce:
1. start ptp4l
2. suspend ptp4l
3. generate 100 link up/down events on a non-PTP interface with "ip link set"
4. resume ptp4l

Actual results:
ptp4l logging error message in an infinite loop

Expected results:
one error message and ptp4l recovering

Additional info:
Upstream fix: https://github.com/richardcochran/linuxptp/commit/ab19bb9a6f25fc13279a0382e46439aacbad761a

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 (linuxptp bug fix and enhancement update), 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-2023:6925