argo: Remove reachable ASSERT_UNREACHABLE

I observed this ASSERT_UNREACHABLE in partner_rings_remove consistently
trip.  It was in OpenXT with the viptables patch applied.

dom10 shuts down.
dom7 is REJECTED sending to dom10.
dom7 shuts down and this ASSERT trips for dom10.

The argo_send_info has a domid, but there is no refcount taken on
the domain.  Therefore it's not appropriate to ASSERT that the domain
can be looked up via domid.  Replace with a debug message.

Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
Reviewed-by: Christopher Clark <christopher.w.clark@gmail.com>
Release-acked-by: Henry Wang <Henry.Wang@arm.com>
This commit is contained in:
Jason Andryuk authored and Andrew Cooper committed 2022-10-14 14:45:41 +01:00
1 parent 171d4d24f8
commit 197f612b77
1 file changed
+2 -1
+2 -1
View File
@@ -1298,7 +1298,8 @@ partner_rings_remove(struct domain *src_d)
ASSERT_UNREACHABLE();
}
else
ASSERT_UNREACHABLE();
argo_dprintk("%pd has entry for stale partner d%u\n",
src_d, send_info->id.domain_id);
if ( dst_d )
rcu_unlock_domain(dst_d);
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.