Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[IPSEC\]\s+fix\s+ref\s+counting\s+in\s+__xfrm4_bundle

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[IPSEC\]\s+fix\s+ref\s+counting\s+in\s+__xfrm4_bundle_create\s*$/: 10 ]

Total 10 documents matching your query.

1. Re: [IPSEC] fix ref counting in __xfrm4_bundle_create() (score: 1): Author: Eugene Surovegin <ebs@xxxxxxxxxxx>; Date: Tue, 1 Jun 2004 13:17:24 -0700; Yes, your version is OK. We haven't got the crash during our testing. Thanks a lot, Herbert. Eugene; /archives/netdev/2004-06/msg00006.html (8,006 bytes)
2. 6.6 (score: 1): Author: xxxxxxx>; Date: Fri, 28 May 2004 17:14:50 -0700; Hi all! I think there is a ref counting bug in error path of __xfrm4_bundle_create(). xfrm_lookup() assumes that xfrm_bundle_create() will take ownership of xfrm_state array passed to it. If xfrm_bun; /archives/netdev/2004-05/msg00441.html (8,801 bytes)
3. ad? (score: 1): Author: eu <romieu@xxxxxxxxxxxxx>; Date: Sat, 29 May 2004 13:27:13 +1000; Well spotted. Hopefully this should finally put an end to all these xfrm_state bug reports :) However, can you see if the following patch fixes this problem as well? It moves the dst->xfrm assignment; /archives/netdev/2004-05/msg00443.html (10,797 bytes)
4. e() (score: 1): Author: n <ebs@xxxxxxxxxxx>; Date: Fri, 28 May 2004 21:21:20 -0700; Yeah, looks much nicer than my version. I'll try to test it tomorrow if I find somebody from QA in the office on Saturday :) or only after a long weekend (test setup is quite complicated and I cannot; /archives/netdev/2004-05/msg00444.html (8,664 bytes)
5. r() (score: 1): Author: r" <davem@xxxxxxxxxx>; Date: Sat, 29 May 2004 12:46:33 -0700; I'm applying this patch. If there is a fixup necessary, just let me know.; /archives/netdev/2004-05/msg00462.html (8,207 bytes)
6. Re: [IPSEC] fix ref counting in __xfrm4_bundle_create() (score: 1): Author: Eugene Surovegin <ebs@xxxxxxxxxxx>; Date: Tue, 1 Jun 2004 13:17:24 -0700; Yes, your version is OK. We haven't got the crash during our testing. Thanks a lot, Herbert. Eugene; /archives/netdev/2004-06/msg00890.html (8,168 bytes)
7. [IPSEC] fix ref counting in __xfrm4_bundle_create() (score: 1): Author: Eugene Surovegin <ebs@xxxxxxxxxxx>; Date: Fri, 28 May 2004 17:14:50 -0700; Hi all! I think there is a ref counting bug in error path of __xfrm4_bundle_create(). xfrm_lookup() assumes that xfrm_bundle_create() will take ownership of xfrm_state array passed to it. If xfrm_bun; /archives/netdev/2004-05/msg00959.html (8,801 bytes)
8. Re: [IPSEC] fix ref counting in __xfrm4_bundle_create() (score: 1): Author: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>; Date: Sat, 29 May 2004 13:27:13 +1000; Well spotted. Hopefully this should finally put an end to all these xfrm_state bug reports :) However, can you see if the following patch fixes this problem as well? It moves the dst->xfrm assignment; /archives/netdev/2004-05/msg00961.html (10,870 bytes)
9. Re: [IPSEC] fix ref counting in __xfrm4_bundle_create() (score: 1): Author: Eugene Surovegin <ebs@xxxxxxxxxxx>; Date: Fri, 28 May 2004 21:21:20 -0700; Yeah, looks much nicer than my version. I'll try to test it tomorrow if I find somebody from QA in the office on Saturday :) or only after a long weekend (test setup is quite complicated and I cannot; /archives/netdev/2004-05/msg00962.html (8,742 bytes)
10. Re: [IPSEC] fix ref counting in __xfrm4_bundle_create() (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Sat, 29 May 2004 12:46:33 -0700; I'm applying this patch. If there is a fixup necessary, just let me know.; /archives/netdev/2004-05/msg00980.html (8,285 bytes)

Current List: 1 - 10
Page: [1]