All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCHSET] IPv4 FIB configuration conversions
Date: Tue, 15 Aug 2006 16:57:23 +0200	[thread overview]
Message-ID: <20060815145723.147333034@postel.suug.ch> (raw)

Replaces the rather ugly struct kern_rta + rtmsg with a new
struct fib_config while converting everything to the new netlink
api. Simplifies the FIB module interface quite a bit and allows
changing internals while keeping a stable netlink interface.

Gets rid of things like passing on netlink_skb_parms all around
the fib code etc.

Also fixes some memory corruptions that could be triggered via
netlink messages, not sure which would actually lead to an oops
though.


             reply	other threads:[~2006-08-15 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 14:57 Thomas Graf [this message]
2006-08-14 22:00 ` [PATCH 1/3] [IPv4]: FIB configuration using struct fib_config Thomas Graf
2006-08-14 22:00 ` [PATCH 2/3] [IPv4]: Convert FIB dumping to use new netlink api Thomas Graf
2006-08-14 22:00 ` [PATCH 3/3] [IPv4]: Convert route get to " Thomas Graf
2006-08-18  1:16 ` [PATCHSET] IPv4 FIB configuration conversions David 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=20060815145723.147333034@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.