netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Timo Teräs" <timo.teras@iki.fi>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, hadi@cyberus.ca, netdev@vger.kernel.org
Subject: Re: [RFC][PATCH] Fixing SA/SP dumps on netlink/af_key
Date: Thu, 17 Jan 2008 14:37:26 +0200	[thread overview]
Message-ID: <478F4C06.4040704@iki.fi> (raw)
In-Reply-To: <20080117.030827.72477184.davem@davemloft.net>

David Miller wrote:
> From: Timo_Teräs <timo.teras@iki.fi>
> Date: Thu, 17 Jan 2008 13:00:09 +0200
> 
>> IMHO, it's a lot better then losing >50% of entries and the end
>> of sequence message on big dumps. SPD and SADB are not that
>> volatile; in most of the cases the dump would be as good as an
>> atomic one.
> 
> I humbly disagree with you.  Interface behavior stability
> is more important.

Small SPDs/SADBs would still be dumped atomically. The patch
affects only the cases when the receive queue is getting full.

>> I'm not sure if there's other major applications that we should
>> be concerned about, but at least ipsec-tools racoon does not
>> expect to get atomic dumps (which btw, comes originally from BSD).
> 
> Racoon was written as an addon to the BSD stack by an IPV6/IPSEC
> project in Japan named KAME, it did not "come from BSD".  It was
> added to BSD.
> 
> There are also other BSD based IPSEC daemons such as the one written
> by the OpenBSD folks.

Yes. I meant that it was originally written to be used in BSD. The
Linux port came later. Sorry for the ambiguous wording.

> I don't think this is arguable at all.  We're not changing semantics
> over what we've done for 4+ years and applications might depend upon.
> It's for a deprecated interface, which makes any semantic changes that
> much less inviting.
> 
> You can argue all you want, but it will not change the invariants in
> the previous paragraph.

True. If no one else agrees with me, I'll drop it. I can always run
my own patched kernel.

I'd appreciate feedback on the xfrm changes. I'll try to make that
part usable patch against net-2.6.25 git tree next week.

      reply	other threads:[~2008-01-17 12:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 12:26 [RFC][PATCH] Fixing SA/SP dumps on netlink/af_key Timo Teräs
2008-01-16 13:52 ` jamal
2008-01-16 14:28   ` Timo Teräs
2008-01-17  1:25     ` jamal
2008-01-16 22:58   ` Herbert Xu
2008-01-17  1:39     ` jamal
2008-01-17  2:17       ` Herbert Xu
2008-01-17  5:54         ` Timo Teräs
2008-01-17 11:11           ` Herbert Xu
2008-01-17 12:21             ` Timo Teräs
2008-01-17 12:26             ` jamal
2008-01-17 12:42           ` jamal
2008-01-17 12:50             ` Herbert Xu
2008-01-17 13:18               ` jamal
2008-01-17 13:31               ` Timo Teräs
2008-01-17 21:34                 ` Herbert Xu
2008-01-18  6:45                   ` Timo Teräs
2008-01-18 14:08                     ` jamal
2008-01-17  6:27     ` Timo Teräs
2008-01-17  7:16       ` David Miller
2008-01-17  7:38         ` Timo Teräs
2008-01-17  7:59           ` David Miller
2008-01-17  8:11             ` Timo Teräs
2008-01-17  8:49               ` David Miller
2008-01-17  9:20                 ` Timo Teräs
2008-01-17  9:31                   ` David Miller
2008-01-17  9:38                     ` Timo Teräs
2008-01-17  9:44                       ` David Miller
2008-01-17 10:01                         ` Timo Teräs
2008-01-17 10:06                           ` David Miller
2008-01-17 11:00                             ` Timo Teräs
2008-01-17 11:08                               ` David Miller
2008-01-17 12:37                                 ` Timo Teräs [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=478F4C06.4040704@iki.fi \
    --to=timo.teras@iki.fi \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    /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).