I've seen that on 2.6.26.4's changelog it says:

commit 464f8f4932d128a3e80402ec85d7c40c1f5e6899
Author: David S. Miller <davem@davemloft.net>
Date: Wed Sep 3 01:03:39 2008 -0700

ipsec: Fix deadlock in xfrm_state management.

[ Upstream commit 37b08e34a98c664bea86e3fae718ac45a46b7276 ]

Ever since commit 4c563f7669c10a12354b72b518c2287ffc6ebfb3
("[XFRM]: Speed up xfrm_policy and xfrm_state walking") it is
illegal to call __xfrm_state_destroy (and thus xfrm_state_put())
with xfrm_state_lock held. If we do, we'll deadlock since we
have the lock already and __xfrm_state_destroy() tries to take
it again.

Fix this by pushing the xfrm_state_put() calls after the lock
is dropped.

Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

Which could be the fix to the hangs I was seeing, I suppose you'll be adding
latest upstream patches to a -5 version of the kernel and thus this patch,
if so, and I'm right about this patch, this bug could then be closed.

Regards...
--
Santiago García Mantiñán



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org