From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Andi Kleen <ak@suse.de>
Cc: Michael Richardson <mcr@sandelman.ottawa.on.ca>,
design@lists.freeswan.org, netdev@oss.sgi.com
Subject: Re: FreeSWAN's pfkey_v2.c
Date: Wed, 16 Oct 2002 23:53:47 -0300 [thread overview]
Message-ID: <20021017025347.GF7541@conectiva.com.br> (raw)
In-Reply-To: <20021017045054.A405@wotan.suse.de>
Em Thu, Oct 17, 2002 at 04:50:54AM +0200, Andi Kleen escreveu:
> > I am looking for confirmation from network stack people that my conclusions
> > from reading of the macros in linux/net.h is correct.
>
> What you should actually do is to add explicit proper SMP locking.
> Then you don't need any SOCKOPS_WRAP hacks.
yup, so that eventually we can kill this hackish bandaid.
- Arnaldo
next prev parent reply other threads:[~2002-10-17 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 2:48 FreeSWAN's pfkey_v2.c Michael Richardson
2002-10-17 2:50 ` Andi Kleen
2002-10-17 2:53 ` Arnaldo Carvalho de Melo [this message]
2002-10-17 3:58 ` Michael Richardson
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=20021017025347.GF7541@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=ak@suse.de \
--cc=design@lists.freeswan.org \
--cc=mcr@sandelman.ottawa.on.ca \
--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).