From: "David S. Miller" <davem@redhat.com>
To: jmorris@intercode.com.au
Cc: toml@us.ibm.com, netdev@oss.sgi.com, kuznet@ms2.inr.ac.ru
Subject: Re: IPSec: setkey -DP freezes machine
Date: Mon, 03 Mar 2003 01:34:51 -0800 (PST) [thread overview]
Message-ID: <20030303.013451.20307573.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303010205360.27480-100000@blackbird.intercode.com.au>
From: James Morris <jmorris@intercode.com.au>
Date: Sat, 1 Mar 2003 03:01:04 +1100 (EST)
Alternatively, a family parameter could be added to the compile_policy()
operation, but this duplicates data already present in our native
xfrm_userpolicy_info format.
I like this solution, it seems the cleanest.
Could someone implement this fix and send me the patch?
I'm very backlogged for the next day or so...
next prev parent reply other threads:[~2003-03-03 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 21:59 IPSec: setkey -DP freezes machine Tom Lendacky
2003-02-28 16:01 ` James Morris
2003-03-03 9:34 ` David S. Miller [this message]
2003-03-03 12:13 ` [PATCH] " James Morris
2003-03-03 12:19 ` David S. Miller
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=20030303.013451.20307573.davem@redhat.com \
--to=davem@redhat.com \
--cc=jmorris@intercode.com.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=toml@us.ibm.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).