From: Stephen Hemminger <shemminger@osdl.org>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com, chas williams <chas@cmf.nrl.navy.mil>
Subject: Re: [PATCH] (1/5) replay netdev notifier events on registration
Date: Wed, 14 Jan 2004 16:44:16 -0800 [thread overview]
Message-ID: <20040114164416.753a62fc.shemminger@osdl.org> (raw)
In-Reply-To: <20040113163631.1a9c1a59.davem@redhat.com>
> Looks good.... are you absolutely sure no remaining notifiers will
> barf if they get a register for an already existing device? I know up
> events should be ok...
Certainty is impossible; but here is what I saw..
Possible problems:
qeth: s390 driver -- bug, code is narcissistic and thinks it only gets
notified about it's own devices.
atm/mpc: only looks for "lec" devices, don't know if they could exist
before it starts.
Unrelated problems:
ddp: registers for notifier before it is initialized
ipmr: no locking for add/delete
ipfwadm: no module owner on /proc interface
The following are okay:
bonding: since must be master or slave can't exist yet
bpqether: patched, was doing replay already
ppoe: only cares about down
dlci: only cares about unregister
lapbether: patched, was doing replay already
vlan: only cares about groups that can't exist yet
aarp: only down
ddp: only cares about down
atm/clip: see additional patch
ax25: only cares about ax25 devices can't exist yet
bridge: only cares about bridged devices can't exist yet
dst: only down
rtnetlink: ok no sockets can be open yet
decnet: see additional patch about startup order
dn_rules: looks okay
econet: only unregister
arp: only address changes
devinet: only inet devices can't exist yet
fib_frontend: looks okay happens before devices anyway
fib_rules: looks okay happens before devices anyway
ipmr: only unregister
ipqueue: only down
ipfwadm: only for chains which can't exist yet
ip6_sockglue: okay
ndisc: patched
ip6: down only
ipx: only for ipx devices which can't exist at initial
irsyms: harmless, whole notify could be removed
netrom: down only
packet: only cares about sockets which can't exist at initial
rose: down only
wanpipe: only cares about sockets which can't exist at initial
x25: only cares about x25 which can't exist yet
xfrm_policy: down only
next prev parent reply other threads:[~2004-01-15 0:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 18:58 [PATCH] (1/5) replay netdev notifier events on registration Stephen Hemminger
2004-01-14 0:36 ` David S. Miller
2004-01-15 0:40 ` [PATCH] decnet initialization race Stephen Hemminger
2004-01-15 8:45 ` David S. Miller
2004-01-15 0:43 ` [PATH] atm/clip device discovery on init not needed Stephen Hemminger
2004-01-15 8:44 ` David S. Miller
2004-01-15 22:59 ` Stephen Hemminger
2004-01-15 23:00 ` David S. Miller
2004-01-15 0:44 ` Stephen Hemminger [this message]
2004-01-15 8:42 ` [PATCH] (1/5) replay netdev notifier events on registration David S. Miller
2004-01-15 18:16 ` Stephen Hemminger
2004-01-15 19:51 ` David S. Miller
2004-01-16 3:19 ` chas williams
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=20040114164416.753a62fc.shemminger@osdl.org \
--to=shemminger@osdl.org \
--cc=chas@cmf.nrl.navy.mil \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.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 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).