mlx5: Fix clock update EBUSY error flow

[ Upstream commit 0819419e791dd9cf9e145353fd97a09c43632f9f ]

mlx5dv_get_clock_info() reads clock data published by the kernel, and is
inherently racy with kernel clock updates. This race cannot be
eliminated; EBUSY will always be possible at some rate when wallclock
timestamping is used with extended CQ polling.

Add documentation for the EBUSY errno so callers know the expected
behavior: EBUSY indicates a CQE is available but the wallclock read
failed. Callers are expected to retry polling the CQ. Providers must not
consume the CQE on EBUSY and must leave the CQ in a valid state for the
next poll attempt.

Prior to this fix, the error was returned after the CQE was parsed, the
consumer index incremented, and WQ/SRQ modified. This left the CQ in an
inconsistent state: the CQE was silently lost and the CQ doorbell was
never updated, making recovery impossible regardless of retries.

Fix by moving the clock update before CQE parsing. At that point only
the consumer index has been advanced, so on failure it can be safely
reverted and EBUSY returned with the CQ intact.

Since EBUSY was previously undocumented and the error path was broken,
no existing user could have relied on this behavior. This fix is
therefore not a behavior change in practice.

Fixes: 4745c8079a86 ("mlx5: Implement read_completion_wallclock_ns")
Signed-off-by: Michael Gur <michaelgur@nvidia.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>