From: David Miller <davem@davemloft.net>
To: johnpol@2ka.mipt.ru
Cc: kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [1/1] netlink: no need to crash if table does not exist.
Date: Tue, 27 Mar 2007 16:41:54 -0700 (PDT) [thread overview]
Message-ID: <20070327.164154.48396509.davem@davemloft.net> (raw)
In-Reply-To: <20070321105847.GA18221@2ka.mipt.ru>
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Date: Wed, 21 Mar 2007 13:58:47 +0300
> On Wed, Mar 21, 2007 at 11:54:45AM +0100, Patrick McHardy (kaber@trash.net) wrote:
> > Evgeniy Polyakov wrote:
> > > We would already do that on init.
> > > Some things become very confused, when nl_table is not used to store
> > > netlink sockets.
> >
> >
> > Its unnecessary, but I don't understand what the problem is.
> > Why would it be NULL and what gets confused?
>
> There is no problem as-is, but I implement unified cache for different
> sockets (currently tcp/udp/raw and netlink are supported), which does
> not use that table, so I currently wrap all access code into special
> ifdefs, this one can be wrapped too, but since it is not needed, it
> saves couple of lines of code.
It is needed. It is there to make sure that a kernel netlink
socket is not created before the af_netlink init code runs.
We've had sequencing bugs like that in the initcall call chain
in the past, that's why the check is there.
next prev parent reply other threads:[~2007-03-27 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 10:44 [1/1] netlink: no need to crash if table does not exist Evgeniy Polyakov
2007-03-21 10:54 ` Patrick McHardy
2007-03-21 10:58 ` Evgeniy Polyakov
2007-03-27 23:41 ` David Miller [this message]
2007-03-28 8:43 ` 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=20070327.164154.48396509.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johnpol@2ka.mipt.ru \
--cc=kaber@trash.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 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).