From: Harald Welte <laforge@netfilter.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: johnpol@2ka.mipt.ru, netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 1 Wire drivers illegally overload NETLINK_NFLOG
Date: Tue, 26 Jul 2005 05:48:28 -0400 [thread overview]
Message-ID: <20050726094828.GJ7925@rama> (raw)
In-Reply-To: <20050724.191505.69244686.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
On Sun, Jul 24, 2005 at 07:15:05PM -0700, David S. Miller wrote:
> > I strongly disrecommend increasing NPROTO. Maybe we should look into
> > reusing NETLINK_FIREWALL (which was an old 2.2.x kernel interface).
>
> ip_queue.c still uses NETLINK_FIREWALL so we really can't use
> that.
sorry, I didn't remember that ip_queue reused the 2.2.x netlink number
:( We should have renamed it to make it clear.
> So instead, as in the patch below, I solved this for now by using
> the NETLINK_SKIP value which was reserved years ago yet never
> made use of.
thanks.
--
- Harald Welte <laforge@netfilter.org> http://netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-26 9:48 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 12:54 [PATCH] 1 Wire drivers illegally overload NETLINK_NFLOG Harald Welte
2005-07-23 3:05 ` YOSHIFUJI Hideaki / 吉藤英明
2005-07-23 3:05 ` YOSHIFUJI Hideaki / 吉藤英明
2005-07-23 3:15 ` YOSHIFUJI Hideaki / 吉藤英明
2005-07-23 3:52 ` Patrick McHardy
2005-07-23 13:33 ` Harald Welte
2005-07-23 13:33 ` Harald Welte
2005-07-25 2:09 ` David S. Miller
2005-07-25 2:09 ` David S. Miller
2005-07-25 2:15 ` David S. Miller
2005-07-25 2:15 ` David S. Miller
2005-07-26 9:48 ` Harald Welte [this message]
2005-07-23 9:14 ` Evgeniy Polyakov
2005-07-25 2:17 ` David S. Miller
2005-07-25 6:02 ` Netlink connector James Morris
2005-07-25 6:02 ` James Morris
2005-07-25 7:06 ` Evgeniy Polyakov
2005-07-25 7:06 ` Evgeniy Polyakov
2005-07-25 14:32 ` Patrick McHardy
2005-07-25 14:32 ` Patrick McHardy
2005-07-25 14:43 ` Eric Leblond
2005-07-25 19:33 ` Evgeniy Polyakov
2005-07-26 8:45 ` Harald Welte
2005-07-26 8:45 ` Harald Welte
2005-07-25 19:28 ` Evgeniy Polyakov
2005-07-25 19:28 ` Evgeniy Polyakov
2005-07-25 23:46 ` Patrick McHardy
2005-07-25 23:46 ` Patrick McHardy
2005-07-25 23:56 ` Thomas Graf
2005-07-26 0:16 ` Patrick McHardy
2005-07-26 0:30 ` Thomas Graf
2005-07-26 0:30 ` Thomas Graf
2005-07-26 4:45 ` Evgeniy Polyakov
2005-07-26 4:45 ` Evgeniy Polyakov
2005-07-26 4:56 ` Stephen Hemminger
2005-07-26 4:56 ` Stephen Hemminger
2005-07-26 5:01 ` Evgeniy Polyakov
2005-07-26 5:01 ` Evgeniy Polyakov
2005-07-26 6:14 ` Thomas Graf
2005-07-26 6:14 ` Thomas Graf
2005-07-26 6:31 ` Evgeniy Polyakov
2005-07-26 6:31 ` Evgeniy Polyakov
2005-07-26 8:42 ` Harald Welte
2005-07-26 8:42 ` Harald Welte
2005-07-26 9:01 ` Evgeniy Polyakov
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=20050726094828.GJ7925@rama \
--to=laforge@netfilter.org \
--cc=davem@davemloft.net \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.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.