| To: | kazunori@xxxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH][IPV6] keeping dst refcnt correctly with using xfrm |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Thu, 05 Jun 2003 22:55:47 -0700 (PDT) |
| Cc: | kuznet@xxxxxxxxxxxxx, usagi@xxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20030606144925.29ad2a9f.kazunori@miyazawa.org> |
| References: | <20030606144925.29ad2a9f.kazunori@miyazawa.org> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Kazunori Miyazawa <kazunori@xxxxxxxxxxxx> Date: Fri, 6 Jun 2003 14:49:25 +0900 In dst_pop refernce cound of dsts except for last are incremented in dst_clone and decremented in next call dst_pop but last dst refernce count will be never decremented. All dst are held by xfrm_policy and there is no need to touch the refernce count here. Ok, so the idea is to hold onto top-level parent DST entry the entire time, and this prevents the DST and all it's children from being destroyed. Is this correct? Let me study this a little bit, I want to make sure it is correct. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH][IPV6] keeping dst refcnt correctly with using xfrm, Kazunori Miyazawa |
|---|---|
| Next by Date: | Re: IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2 (in)compatible encryption methods, Peter Bieringer |
| Previous by Thread: | [PATCH][IPV6] keeping dst refcnt correctly with using xfrm, Kazunori Miyazawa |
| Next by Thread: | Re: [PATCH][IPV6] keeping dst refcnt correctly with using xfrm, Kazunori Miyazawa |
| Indexes: | [Date] [Thread] [Top] [All Lists] |