netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Xianpeng Zhao" <673321875@qq.com>
To: "Steffen Klassert" <steffen.klassert@secunet.com>
Cc: netdev <netdev@vger.kernel.org>, alan <alan@lxorguk.ukuu.org.uk>
Subject: Re: Fw:[Bug 70471] xfrm policy node will double unlink.
Date: Thu, 20 Feb 2014 10:01:19 +0800	[thread overview]
Message-ID: <tencent_0260B87B11A1005909F5BB41@qq.com> (raw)
In-Reply-To: <20140219114326.GE32371@secunet.com>

Sorry, I misunderstood your means in last mail.
    I get your patch now. Later I will use your patch. 

    Now, I am using my patch doing the test, my patch is like this; till now, everything is OK. I think my patch almost same with your patch.

diff --git a/include/linux/list.h b/include/linux/list.h
index cc6d2aa..3a8b95a 100644
--- a/include/linux/list.h
+++ b/include/linux/list.h
@@ -578,6 +578,11 @@ static inline int hlist_unhashed(const struct hlist_node *h)
 	return !h->pprev;
 }
 
+static inline int hlist_removed(const struct hlist_node *h)
+{
+	return (h->pprev == LIST_POISON2 && h->next == LIST_POISON1);
+}
+
 static inline int hlist_empty(const struct hlist_head *h)
 {
 	return !h->first;
diff --git a/net/xfrm/xfrm_policy.c b/net/xfrm/xfrm_policy.c
index 41eabc4..005be47 100644
--- a/net/xfrm/xfrm_policy.c
+++ b/net/xfrm/xfrm_policy.c
@@ -1073,7 +1073,7 @@ static struct xfrm_policy *__xfrm_policy_unlink(struct xfrm_policy *pol,
 {
 	struct net *net = xp_net(pol);
 
-	if (hlist_unhashed(&pol->bydst))
+	if (hlist_unhashed(&pol->bydst) || hlist_removed(&pol->bydst))
 		return NULL;
 
 	hlist_del(&pol->bydst);


 




------------------ Original ------------------
From:  "Steffen Klassert";<steffen.klassert@secunet.com>;
Date:  Wed, Feb 19, 2014 07:43 PM
To:  "Xianpeng Zhao"<673321875@qq.com>; 
Cc:  "netdev"<netdev@vger.kernel.org>; "alan"<alan@lxorguk.ukuu.org.uk>; 
Subject:  Re: Fw:[Bug 70471] xfrm policy node will double unlink.



On Wed, Feb 19, 2014 at 10:07:14AM +0800, Xianpeng Zhao wrote:
> Hi Steffen,
> 
>       This problem is happened when running stress test; Very little chance can get this case.
> 
>       As you say, add a long time sleep in function xfrm_policy_bysel_ctx between __xfrm_policy_unlink and 
> xfrm_policy_kill, will reproduce this issue manually. 
> 
>       About my patch, I am not sure it is OK, because after it patched, the issue had reproduced once, but after some days test recently, have not reproduced again. 
> 
>       But I can make sure when __xfrm_policy_unlink find the node had been removed, return NULL instead of delete again will fix this problem.
> 
>       What's your suggestions?
> 

Please test the patch I've sent with the last mail.
Thanks!
.

  reply	other threads:[~2014-02-20  2:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18  2:55 Fw:[Bug 70471] xfrm policy node will double unlink Xianpeng Zhao
2014-02-18  8:37 ` Steffen Klassert
2014-02-19  2:07   ` Xianpeng Zhao
2014-02-19 11:43     ` Steffen Klassert
2014-02-20  2:01       ` Xianpeng Zhao [this message]
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_0260B87B11A1005909F5BB41@qq.com \
    --to=673321875@qq.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.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;
as well as URLs for NNTP newsgroup(s).