Claude review: drm/xe: use krealloc_array to prevent integer overflow

[Claude Code Review Bot <claude-review@example.com>]

Patch Review

**Correctness:** The transformation is mechanically correct in both hunks. The arguments are split properly: the original `count * sizeof(u32)` becomes `count, sizeof(u32)`, and `max_vmas * sizeof(*madvise_range->vmas)` becomes `max_vmas, sizeof(*madvise_range->vmas)`.

**Commit message nit:** The subject says "prevent integer overflow" which slightly overstates the risk. Both call sites have values bounded well below overflow thresholds. A more accurate subject would be something like "use krealloc_array to guard against potential integer overflow" or "use krealloc_array for overflow-safe allocation". This is a minor style point.

**Signed-off-by ordering:** The patch has:
```
Signed-off-by: Baoli.Zhang <baoli.zhang@linux.intel.com>
Signed-off-by: Junxiao.Chang <junxiao.chang@intel.com>
```
The `From:` header shows Baoli.Zhang as the author, so Junxiao.Chang's Signed-off-by appearing second (after the author) implies Junxiao.Chang is forwarding the patch. If Junxiao.Chang is a co-developer rather than a submitter in the chain, a `Co-developed-by:` + `Signed-off-by:` pair would be more appropriate.

**xe_vm_madvise.c alignment:** The alignment of the continuation arguments is slightly off from the opening parenthesis convention:
```c
__vmas = krealloc_array(madvise_range->vmas,
                  max_vmas,
                  sizeof(*madvise_range->vmas),
                  GFP_KERNEL);
```
The arguments after the first line are indented with tabs+spaces to roughly column-align, but they don't align with the first argument after the opening `(`. This is a minor style issue — matching the existing indentation style of the surrounding code is fine.

**Overall:** A straightforward and correct cleanup patch. No functional concerns. Recommend accepting with optional minor commit message adjustment.

---
Generated by Claude Code Patch Reviewer