All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: "Pavel A. Nekrasov" <pnekrasov@gmail.com>
Cc: Harald Welte <laforge@netfilter.org>,
	netfilter-devel@lists.netfilter.org,
	Patrick McHardy <kaber@trash.net>
Subject: Re: [1/1] OSF: pom-ng - linux-2.6.
Date: Wed, 08 Dec 2004 16:43:49 +0300	[thread overview]
Message-ID: <1102513429.3363.71.camel@uganda> (raw)
In-Reply-To: <fa78a99804120805326fed423b@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

On Wed, 2004-12-08 at 14:32 +0100, Pavel A. Nekrasov wrote:
> i got you doing the same.
> 
> Evgeniy Polyakov wrote:
> 
> >+      nts = netlink_kernel_create(NETLINK_NFLOG, NULL);
> 
> drivers/w1/w1_int.c:    dev->nls = netlink_kernel_create(NETLINK_NFLOG, NULL);
> 
> NETLINK_NFLOG is used by ipt_ULOG, you can't use that socket because
> you are breaking compatibility. You have to use different sockets,
> call davem and request new ones.

No, ipt_osf used this number forever.
And it was discussed with Harald some time ago.

Allocating new socket number for any new driver that want to communicate
over netlink is badly broken idea.
I've created so called "kernel connector" aka ioctl-ng to solve this
problem,  and this patch is flying around for some time, but until it
is 
committed we should not break old compatibility issues.

> kind regards,
> Pavel
-- 
        Evgeniy Polyakov

Crash is better than data corruption -- Arthur Grabowski

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-12-08 13:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 10:58 [1/1] OSF: pom-ng - linux-2.6 Evgeniy Polyakov
2004-12-08 11:02 ` Evgeniy Polyakov
2004-12-08 18:48   ` Patrick McHardy
2004-12-12 15:13     ` Evgeniy Polyakov
2005-01-02 23:31       ` Patrick McHardy
2004-12-08 13:32 ` Pavel A. Nekrasov
2004-12-08 13:43   ` Evgeniy Polyakov [this message]
2004-12-08 18:44 ` Patrick McHardy

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=1102513429.3363.71.camel@uganda \
    --to=johnpol@2ka.mipt.ru \
    --cc=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pnekrasov@gmail.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 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.