|SUCCESS| test: fix 5-fragment IP reassembly test vectors

[dpdklab at iol.unh.edu]

Test-Label: ai-code-review
Test-Status: SUCCESS
https://dpdk.org/patch/169705

_AI Code Review_

=== Patch Review: series.patch (via Claude) ===
Review date: 2026-09-17

# Review of DPDK Patch: test: fix 5-fragment IP reassembly test vectors

## Summary
This patch corrects test vector data in IP reassembly test packets. The changes fix UDP source port bytes and an IPv6 next_header field. This is test-only code with no functional impact on DPDK libraries or drivers.

---

## Findings

### Errors
None.

### Warnings
None.

### Info

**Test vector corrections appear valid**

The patch makes three byte-level corrections to static test packet structures:

1. **IPv6 full packet next_header** (`0x2c` - `0x11`): Changes from Fragment Header (44) to UDP (17), which is correct for a reassembled packet that should directly contain UDP, not a fragment header.

2. **UDP source ports in first fragments** (`0x80 0x00` - `0x08 0x00`): Changes port from 32768 (0x8000 big-endian) to 2048 (0x0800 big-endian). Without seeing the original test design intent or corresponding fragments, this appears to be correcting byte-swapped test data.

The changes are confined to test data initialization and do not affect runtime logic.

---

## Code Quality Check

- [x] No correctness bugs (test data only)
- [x] No style violations (data array initialization)
- [x] No forbidden tokens
- [x] No API changes
- [x] No documentation required (test-only)
- [x] No release notes required (test-only, per guidelines)
- [x] Proper Fixes: tag present
- [x] Cc: stable at dpdk.org present

---

## Conclusion

The patch is acceptable. The byte-level corrections to test vectors appear valid based on protocol field definitions (IPv6 next_header 0x11=UDP is correct for reassembled packets; UDP source port byte order correction is reasonable). Since this only affects test data initialization and not executable logic, the risk is minimal.

No changes required.