This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.
Bug 2040815 - [RFE] Add MTU Oversize Message To OVS
Summary: [RFE] Add MTU Oversize Message To OVS
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux Fast Datapath
Classification: Red Hat
Component: openvswitch
Version: RHEL 8.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Maxime Coquelin
QA Contact: qding
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-14 18:28 UTC by Jamie Fargen
Modified: 2024-03-12 11:50 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-03-12 11:50:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   FD-1719 0 None None None 2024-03-12 11:50:02 UTC

Description Jamie Fargen 2022-01-14 18:28:54 UTC 
Description of problem:
There is no log message generated in the case of an ovs port, bridge, etc which drops a packet because of an oversize MTU.


How reproducible:
Create a KVM instance using the Virtio driver and configure the MTU larger than bridge or port the instance is attached and send packets larger than this egress interface. Nothing will be logged on the KVM hypervisor.

Expected results:
Expect the hypervisor to log a message to kernel ring buffer.

Additional info:
There has been some work suggested for other driver like the Intel i40 driver.
https://www.spinics.net/lists/netdev/msg719280.html
Comment 2 Eelco Chaudron 2022-11-16 10:49:03 UTC 
So I assume this needs to be assigned to the hypervisor team? Or do we need something specific from the kernel driver, then it needs to go to the Kernel team?

Maxime as this might be more in your area, can you add a comment, and re-assign it to the correct team?
Comment 3 Flavio Leitner 2024-03-12 11:50:02 UTC 
Migrated to  https://issues.redhat.com/browse/FDP-470
Note You need to log in before you can comment on or make changes to this bug.