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 11:20:42 +0200	[thread overview]
Message-ID: <478F1DEA.5070903@iki.fi> (raw)
In-Reply-To: <20080117.004900.58497170.davem@davemloft.net>

David Miller wrote:
> From: Timo_Teräs <timo.teras@iki.fi>
> Date: Thu, 17 Jan 2008 10:11:17 +0200
> 
>> I thought my patch would qualify as "life support" bug fix.
>> Currently racoon fails to work if there are too many SPDs or SAs
>> because the kernel cannot handle the dump request properly. And this
>> is what my patch fixes for pfkey. It adds no new features or
>> functionality; just makes the dumping work with large databases.
> 
> Racoon should use netlink for reasons far and beyond the
> problem you are trying to address.

Yes. But this is fairly major thing to do. One needs to create
API abstraction layer (still need to use pfkey in *BSD). Test it.
A lot of work that is not going to happen very soon.

Where as the pfkey bug fix is non-intrusive and helps all
legacy applications still using af_key by _fixing a bug in
kernel_.

> The dumping behavior of AF_KEY is just horrific, as one of
> several examples.

If af_key is all that bad and does not qualify to get maintanace
bug fixes, why not remove it complitely?

That would make userland adapt faster.

>> Then there's also the xfrm dumping changes which change the
>> algorithm from O(n^2) to O(n) with some memory overhead, but
>> that is a different story. Any comments on that?
> 
> I have no general objections to those changes although I am
> backlogged and thus have not studied them in detail.  Jamal
> is having what appears to be a healthy dialogue with you about
> the details so I'm not concerned much :)

Ok. I hope someone can also give feedback on the naming
conventions. And about the api changes to xfrm policy/state
walking.

- Timo


  reply	other threads:[~2008-01-17  9:19 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 [this message]
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

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=478F1DEA.5070903@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).