From: Patrick McHardy <kaber@trash.net>
To: k8 s <uint32@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is this a bug in linux-2.6.12 ipsec code function xfrm4_rcv_encap ??
Date: Sat, 23 Jul 2005 03:55:24 +0200 [thread overview]
Message-ID: <42E1A38C.80806@trash.net> (raw)
In-Reply-To: <699a19ea050722183117eec7a9@mail.gmail.com>
k8 s wrote:
> I AM SORRY FOR THE PREVIOUS MAIL.
> I am correcting my previous mail.
> Infact I see only One race(not three as was wrongly pointed out).
> I commented out the section once again where the race might be.
>
> /********************************************************
> Race Here . The Check(x->props.mode) is without Lock. What if setkey
> -F is done at the same time on another processor freeing what x points
> to.
> ********************************************************/
>
>> if (x->props.mode) {
We hold a reference to the state, so it can't be freed.
prev parent reply other threads:[~2005-07-23 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 1:07 Is this a bug in linux-2.6.12 ipsec code function xfrm4_rcv_encap ?? k8 s
2005-07-23 1:31 ` k8 s
2005-07-23 1:55 ` Patrick McHardy [this message]
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=42E1A38C.80806@trash.net \
--to=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=uint32@gmail.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