From: "Xianpeng Zhao" <673321875@qq.com>
To: netdev <netdev@vger.kernel.org>
Cc: alan <alan@lxorguk.ukuu.org.uk>
Subject: Fw:[Bug 70471] xfrm policy node will double unlink.
Date: Tue, 18 Feb 2014 10:55:57 +0800 [thread overview]
Message-ID: <tencent_0D7FA5355C7998793C100B23@qq.com> (raw)
Hi Group,
I found a problem about xfrm policy.
In corner case, xfrm policy node will be double unlinked from the list.
The scenario like this:
In thread context, After removed the node from list, before remove the xfrm policy expire timer. At this point, a timer interrupt come, and call the run_timer_softirq to execute the xfrm_policy_timer to remove the expired policy node; because this policy node had already removed from list. this remove will cause the node double unlinked.
I have done such patch to protect this case. I am not sure here the policy->walk.dead means. From the name, I think it mark the policy node was dead. Maybe I use this flag is not correct, please the expert correct me if I am wrong. More detail information can reference bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=70471
my patch:
--- net/xfrm/xfrm_policy.c_old 2014-02-10 10:18:28.421504317 +0800
+++ net/xfrm/xfrm_policy.c 2014-02-10 10:19:01.661503334 +0800
@@ -330,7 +330,6 @@ static void xfrm_queue_purge(struct sk_b
static void xfrm_policy_kill(struct xfrm_policy *policy)
{
- policy->walk.dead = 1;
atomic_inc(&policy->genid);
@@ -1156,6 +1155,7 @@ static struct xfrm_policy *__xfrm_policy
if (hlist_unhashed(&pol->bydst))
return NULL;
+ pol->walk.dead = 1;
hlist_del(&pol->bydst);
hlist_del(&pol->byidx);
list_del(&pol->walk.all);
------------------
Best Regards
Xianpeng
next reply other threads:[~2014-02-18 3:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 2:55 Xianpeng Zhao [this message]
2014-02-18 8:37 ` Fw:[Bug 70471] xfrm policy node will double unlink Steffen Klassert
2014-02-19 2:07 ` Xianpeng Zhao
2014-02-19 11:43 ` Steffen Klassert
2014-02-20 2:01 ` Xianpeng Zhao
2014-02-21 7:35 ` Steffen Klassert
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=tencent_0D7FA5355C7998793C100B23@qq.com \
--to=673321875@qq.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).