Bug#497796: maybe solved upstream?
I've seen that on 220.127.116.11's changelog it says:
Author: David S. Miller <email@example.com>
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
Fix this by pushing the xfrm_state_put() calls after the lock
Signed-off-by: David S. Miller <firstname.lastname@example.org>
Signed-off-by: Greg Kroah-Hartman <email@example.com>
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.
Santiago García Mantiñán
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
|All times are GMT. The time now is 11:12 AM.|
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.