Re: [PATCH v7 6/6] s390/vfio-ap: replace guest-reachable WARNs with ratelimited warnings and add dmesg visibility to DBF_WARNs

[sashiko-bot@kernel.org]

> WARN and WARN_ONCE macros in code paths reachable by a guest
> can be triggered repeatedly by a malicious or misbehaving guest,
> flooding the kernel log and potentially impacting system
> stability. Replace all WARN and WARN_ONCE calls reachable from
> the guest AP interrupt enable/disable and queue reset paths with
> ratelimited warning functions. When the queue is assigned to
> an mdev, dev_warn_ratelimited() is used so the mdev device name
> (which includes the UUID) appears in the message. Otherwise,
> pr_warn_ratelimited() is used.
> 
> Four reporting functions are introduced:
> 
> report_tapq_rc() - reports an invalid or unexpected response
> code from PQAP(TAPQ). Used in vfio_ap_wait_for_irqclear() and
> apq_status_check(). The signatures of both functions are changed
> [ ... ]
> dmesg log entries ensure that warning conditions are immediately
> visible in the kernel log without requiring familiarity with
> the s390 debug feature infrastructure.
> 
> Signed-off-by: Anthony Krowiak <akrowiak@linux.ibm.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260904223531.1611088-1-akrowiak@linux.ibm.com?part=6