From: Steffen Klassert <steffen.klassert@secunet.com>
To: Tristan Madani <tristmd@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Christian Hopps <chopps@labn.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, <netdev@vger.kernel.org>,
<stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xfrm: iptfs: fix ABBA deadlock in iptfs_destroy_state()
Date: Tue, 2 Jun 2026 12:06:01 +0200 [thread overview]
Message-ID: <ah6rCd7up8i6173I@secunet.com> (raw)
In-Reply-To: <20260528160318.2631699-1-tristan@talencesecurity.com>
On Thu, May 28, 2026 at 04:03:18PM +0000, Tristan Madani wrote:
> iptfs_destroy_state() calls hrtimer_cancel() while holding a spinlock
> that the timer callback also acquires, leading to an ABBA deadlock on
> SMP systems.
>
> For the output timer (iptfs_timer):
> - iptfs_destroy_state() holds x->lock, calls hrtimer_cancel()
> - iptfs_delay_timer() callback takes x->lock
>
> For the drop timer (drop_timer):
> - iptfs_destroy_state() holds drop_lock, calls hrtimer_cancel()
> - iptfs_drop_timer() callback takes drop_lock
>
> Both timers use HRTIMER_MODE_REL_SOFT, so their callbacks run in softirq
> context. When hrtimer_cancel() is called for a soft timer that is
> currently executing on another CPU, hrtimer_cancel_wait_running() spins
> on softirq_expiry_lock -- the same lock held by the softirq running the
> callback. If the callback is blocked waiting for the spinlock held by
> the caller of hrtimer_cancel(), a circular dependency forms:
>
> CPU 0: holds lock_A -> waits for softirq_expiry_lock
> CPU 1: holds softirq_expiry_lock -> waits for lock_A
>
> Fix this by cancelling both timers before acquiring their respective
> locks. hrtimer_cancel() is safe to call without holding any lock and
> will wait for any in-progress callback to complete. The locks are still
> acquired afterwards to synchronize with any in-flight packet processing
> before tearing down the state.
>
> Found by source code audit.
>
> Fixes: 4b3faf610cc6 ("xfrm: iptfs: add new iptfs xfrm mode impl")
> Cc: Christian Hopps <chopps@labn.net>
> Cc: Steffen Klassert <steffen.klassert@secunet.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Tristan Madani <tristan@talencesecurity.com>
> ---
> net/xfrm/xfrm_iptfs.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/net/xfrm/xfrm_iptfs.c b/net/xfrm/xfrm_iptfs.c
> index 97bc979e55baf..fd25b2b230793 100644
> --- a/net/xfrm/xfrm_iptfs.c
> +++ b/net/xfrm/xfrm_iptfs.c
> @@ -2708,8 +2708,9 @@ static void iptfs_destroy_state(struct xfrm_state *x)
> if (!xtfs)
> return;
>
> - spin_lock_bh(&xtfs->x->lock);
> hrtimer_cancel(&xtfs->iptfs_timer);
> +
> + spin_lock_bh(&xtfs->x->lock);
> __skb_queue_head_init(&list);
> skb_queue_splice_init(&xtfs->queue, &list);
> spin_unlock_bh(&xtfs->x->lock);
> @@ -2717,8 +2718,9 @@ static void iptfs_destroy_state(struct xfrm_state *x)
> while ((skb = __skb_dequeue(&list)))
> kfree_skb(skb);
>
> - spin_lock_bh(&xtfs->drop_lock);
> hrtimer_cancel(&xtfs->drop_timer);
> +
> + spin_lock_bh(&xtfs->drop_lock);
> spin_unlock_bh(&xtfs->drop_lock);
What is this? You take the drop_lock just to release it in the next
line.
prev parent reply other threads:[~2026-06-02 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 16:03 [PATCH] xfrm: iptfs: fix ABBA deadlock in iptfs_destroy_state() Tristan Madani
2026-06-02 10:06 ` Steffen Klassert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ah6rCd7up8i6173I@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=chopps@labn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tristmd@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox