All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Robert Scott <rbscott@axentra.net>, bridge@lists.osdl.org
Subject: Re: [Bridge] unregister_netdevice: waiting for br0 to become free. Usage count = 1 (2.6.12.3)
Date: Wed, 31 Aug 2005 22:12:33 -0700	[thread overview]
Message-ID: <43168DC1.6010806@candelatech.com> (raw)
In-Reply-To: <20050831213749.6bc8dd50@localhost.localdomain>

Stephen Hemminger wrote:

> Two other recent reports are:
> 1. Buggy applications that hold packets in their input queue forever,
>    and/or netfilters.  The socket buffer's contain a reference for
>    packets in flight.

Surely the sockets listen for the net-unregister event and clean
themselves up???  An app shouldn't be able to hang the kernel
like this...

> 2. The VLAN code had a number of reference bugs, if you look through
>    recent netdev mailing list you will see the discussion.

Could be VLAN code, but my debug patch seems to implicate the ref
leaks in neighbor.c....  I also reproduced with another type of VLANs
other than 802.1q...

Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2005-09-01  5:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01  2:04 [Bridge] unregister_netdevice: waiting for br0 to become free. Usage count = 1 (2.6.12.3) Robert Scott
2005-09-01  4:26 ` Ben Greear
2005-09-01  4:37 ` Stephen Hemminger
2005-09-01  5:12   ` Ben Greear [this message]
2005-09-01  6:33   ` Robert Scott
2005-09-01 16:24     ` Stephen Hemminger
2005-09-01 19:04   ` Patrick McHardy
  -- strict thread matches above, loose matches on Subject: below --
2005-09-02  7:37 Louis Croisez
2015-06-26 12:04 Jorge Dominguez

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=43168DC1.6010806@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=bridge@lists.osdl.org \
    --cc=rbscott@axentra.net \
    --cc=shemminger@osdl.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 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.