Re: [PATCH v5 0/6] scsi: mvumi: bound the values the firmware supplies

[Yehyeong Lee]

Superseded by [PATCH v6 0/5],
<20261014162413.3649841-1-yhlee@xxxxxxxxxxxxxxxxxx>.

The real defects the reviews on this series found are fixed there: the
target/LUN alias from 6/6 is now a device-count bound in 4/5, the shift
counts 4/5 checks are read with READ_ONCE() so the checked value is the
shifted one, the hotplug bitmap is bounded by the transfer length rather
than the buffer, and the response frame tag is validated where it is used.

The rest I did not change, and the v6 cover letter says why: the driver has
no device-to-host endianness conversion anywhere, so converting one field
would be inconsistent; the bitmap alignment, the size >> 3 overlap and the
truncating shift in mvumi_delete_internal_cmd() are pre-existing and want
their own patches; keeping the sizes across a shrinking reset is correct
because the driver is what publishes them; and there is no ordering pair
for a dma_rmb() to protect.