|SUCCESS| net/mlx5: restore fake mbuf guards on Rx replenish failure

[dpdklab at iol.unh.edu]

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

_AI Code Review_

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

# DPDK Patch Review

## Summary

This patch fixes a correctness bug in the mlx5 PMD's vectorized Rx path where mempool allocation failures can leave stale mbuf pointers in guard slots, leading to potential metadata corruption.

---

## Errors

None.

---

## Warnings

None.

---

## Info

### Positive Observations

**Correctness**: The patch correctly identifies and fixes a use-after-free scenario:
- The mempool get path can partially fill the output array from cache before failing on the backend fetch
- Without restoration, guard slots point to mbufs still owned by the mempool
- Later allocations can give those mbufs to the application, after which vectorized CQE processing corrupts them through stale pointers
- The fix restores the four fake mbuf guards on allocation failure, preventing this corruption

**Style compliance**:
- Loop variable `i` properly declared
- Comments are clear and explain the non-obvious behavior
- Code follows DPDK indentation (tabs) and brace style
- Proper `Fixes:` tag and `Cc: stable at dpdk.org`

**Process compliance**:
- Patch structure is appropriate for a bug fix
- `.mailmap` update for new author is included
- No new API, no experimental features, suitable for backport

---

## Conclusion

**This patch is correct and ready for integration.** It fixes a real correctness bug (potential metadata corruption through stale pointers after partial mempool allocation failure) with minimal overhead (restoration only on the failure path). The fix applies to both regular and MPRQ vector Rx paths and is appropriate for stable backport.