mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-bluefield (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
SRU Justification:
[Impact]
This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets.
[Fix]
Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck.
[Test Case]
Same functionality and testing as on BlueField-1/2/3. No functionality change.
Add negative tests:
1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck.
2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck.
[Regression Potential]
Same behavior from user perspective.
Changed in linux-bluefield (Ubuntu): | |
status: | New → Invalid |
Changed in linux-bluefield (Ubuntu Focal): | |
status: | New → Fix Committed |
Changed in linux-bluefield (Ubuntu Jammy): | |
status: | New → Fix Committed |
tags: |
added: verification-done-jammy removed: verification-needed-jammy |
tags: |
added: verification-done-focal removed: verification-needed-focal |
Fixes have been posted for review for both Jammy and Focal.