mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Patrick Toal <ptoal@cisco.com>
To: linux-kernel@vger.kernel.org
Subject: RE: Cisco vpnclient prevents proper shutdown starting with 2.6.2
Date: Sun, 22 Feb 2004 20:33:38 -0500	[thread overview]
Message-ID: <1077500017.1746.13.camel@ptoal-pc> (raw)

Sid Boyce wrote:
> I tried using this client with up to 2.6.1-mm5 and ended up with Dead
> processes for cvpnd and vpnclient, nothing else was affected, went
> back to 2.4.x kernel.
> Regards
> Sid

Sid, et al. 

First, before anyone starts deluging me with questions, you should know
that even though my details say Cisco, I am an SE in the field, _not_ a
developer.  Second, please reply to me off-list, as I do not subscribe
to the LK list.  

That being said, I think I've tracked this down to a recent change in
the net/core/dev.c file.  I reversed the patch to
register_netdevice_notifier below, and the vpnclient now works fine. 
This is called by the handle_vpnup routine in interceptor.c of the
vpnclient kernel module.

I am _not_ a kernel developer, nor do I spend the majority of my time
programming, so I haven't been able to figure out _why_ these changes
cause the module to freeze.  I'd be interested if anyone could tell me
the answer to that question. :-)

Regards,
Patrick

@@ -946,11 +996,29 @@
  *     The notifier passed is linked into the kernel structures and must
  *     not be reused until it has been unregistered. A negative errno code
  *     is returned on a failure.
+ *
+ *     When registered all registration and up events are replayed
+ *     to the new notifier to allow device to have a race free
+ *     view of the network device list.
  */
 
 int register_netdevice_notifier(struct notifier_block *nb)
 {
-       return notifier_chain_register(&netdev_chain, nb);
+       struct net_device *dev;
+       int err;
+
+       rtnl_lock();
+       err = notifier_chain_register(&netdev_chain, nb);
+       if (!err) {
+               for (dev = dev_base; dev; dev = dev->next) {
+                       nb->notifier_call(nb, NETDEV_REGISTER, dev);
+
+                       if (dev->flags & IFF_UP)
+                               nb->notifier_call(nb, NETDEV_UP, dev);
+               }
+       }
+       rtnl_unlock();
+       return err;
 }
 
 /**


-- 
Patrick J. Toal, Systems Engineer, CCCS
Cisco Systems Canada Co.
181 Bay Street, Bay Wellington Tower, Suite 3400
Toronto, Ontario, Canada M5J 2T3
Phone: 416-306-7735     Pager: 1-800-682-4726


             reply	other threads:[~2004-02-23  1:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23  1:33 Patrick Toal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-27  0:30 Sid Boyce
2004-02-24 20:41 Gertjan van Wingerde
2004-02-25  3:46 ` Eugene Teo
     [not found] <fa.fds2rgj.110cgg9@ifi.uio.no>
2004-02-24 15:50 ` jhp
2004-02-07 21:20 Sid Boyce
2004-02-07  5:17 Meinhard E. Mayer
2004-02-07  9:10 ` Eduard Bloch
2004-02-08 16:05 ` Rik van Riel

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=1077500017.1746.13.camel@ptoal-pc \
    --to=ptoal@cisco.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®