From: Eugene Surovegin <ebs@ebshome.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@oss.sgi.com, davem@redhat.com
Subject: Re: [IPSEC] fix ref counting in __xfrm4_bundle_create()
Date: Fri, 28 May 2004 21:21:20 -0700 [thread overview]
Message-ID: <20040529042120.GA3623@gate.ebshome.net> (raw)
In-Reply-To: <E1BTuV7-0002m2-00@gondolin.me.apana.org.au>
On Sat, May 29, 2004 at 01:27:13PM +1000, Herbert Xu wrote:
> However, can you see if the following patch fixes this problem as well?
> It moves the dst->xfrm assignment to a spot where errors cannot occur.
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 reproduce it at home).
Eugene.
next prev parent reply other threads:[~2004-05-29 4:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 0:14 [IPSEC] fix ref counting in __xfrm4_bundle_create() Eugene Surovegin
2004-05-29 3:27 ` Herbert Xu
2004-05-29 4:21 ` Eugene Surovegin [this message]
2004-05-29 19:46 ` David S. Miller
2004-06-01 20:17 ` Eugene Surovegin
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=20040529042120.GA3623@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=davem@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.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).