From: "David S. Miller" <davem@redhat.com>
To: maxk@qualcomm.com
Cc: jajcus@bnet.pl, linux-kernel@vger.kernel.org
Subject: Re: "new style" netdevice allocation patch for TUN driver (2.4.18 kernel)
Date: Tue, 06 Aug 2002 10:07:49 -0700 (PDT) [thread overview]
Message-ID: <20020806.100749.21530590.davem@redhat.com> (raw)
In-Reply-To: <5.1.0.14.2.20020806094253.09734790@mail1.qualcomm.com>
From: "Maksim (Max) Krasnyanskiy" <maxk@qualcomm.com>
Date: Tue, 06 Aug 2002 10:07:49 -0700
Dave, how about this
--- net/core/dev.c.orig Mon Aug 5 21:48:54 2002
+++ net/core/dev.c Mon Aug 5 21:54:01 2002
@@ -2577,6 +2577,11 @@
First, the call-chain notifiers are probably not safe
to run without rtnl_lock held.
Second, why not just fix the bug instead of applying band-aids
to device unregistry? I know it's nice in that it allows you
to configure devices some more, but it doesn't make the real
problem go away.
next prev parent reply other threads:[~2002-08-06 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 13:35 "new style" netdevice allocation patch for TUN driver (2.4.18 kernel) Jacek Konieczny
2002-08-01 17:43 ` kuznet
2002-08-01 17:52 ` Jacek Konieczny
2002-08-01 18:01 ` kuznet
2002-08-02 0:27 ` two net_device ? ??
2002-08-02 23:54 ` "new style" netdevice allocation patch for TUN driver (2.4.18 kernel) Maksim (Max) Krasnyanskiy
[not found] ` <20020803140858.GA5314@nic.nigdzie>
2002-08-06 17:07 ` Maksim (Max) Krasnyanskiy
2002-08-06 17:07 ` David S. Miller [this message]
2002-08-06 20:03 ` Maksim (Max) Krasnyanskiy
2002-08-06 17:29 ` Jacek Konieczny
-- strict thread matches above, loose matches on Subject: below --
2002-08-01 13:35 Jacek Konieczny
2002-08-07 3:10 Julian Anastasov
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=20020806.100749.21530590.davem@redhat.com \
--to=davem@redhat.com \
--cc=jajcus@bnet.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.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.