netdev - Re: removing a bonding_master (ver 3.3.0 driver) results in leftover kernel process?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <883.1242404350@death.nxdomain.ibm.com>
Date:	Fri, 15 May 2009 09:19:10 -0700
From:	Jay Vosburgh <fubar@...ibm.com>
To:	Deepjyoti Kakati <dkakati73@...il.com>
cc:	netdev@...r.kernel.org
Subject: Re: removing a bonding_master (ver 3.3.0 driver) results in leftover kernel process?

Deepjyoti Kakati <dkakati73@...il.com> wrote:

>using bonding driver ver 3.3.0 (on fedora 10)
>
>I am using the sysfs  to add a couple of interfaces as bonding_masters
>and repeatedly removing and adding  during test cycles as in:
>
>echo +bond_data > /sys/class/net/bonding_masters
>..add slave eth ports..
>...do work...
>......
>echo -bond_data > /sys/class/net/bonding_masters
>
>every time I add it, seems to start a kernel process named after that
>bond interface
>but when removing, that proc is not killed.
>
>it builds up after a period of testing and even kill -9/kill -15 isnt
>killing them
>
>Am I doing something wrong ? Can I prevent the buildup of these unwanted
>processes that are presumably consuming resources ?

	Upgrade your kernel, this problem was fixed by the following:

commit a434e43f3d844192bc23bd7b408bac979c40efe7
Author: Jay Vosburgh <fubar@...ibm.com>
Date:   Thu Oct 30 17:41:15 2008 -0700

    bonding: Clean up resource leaks
    
    This patch reworks the resource free logic performed at the time
    a bonding device is released.  This (a) closes two resource leaks, one
    for workqueues and one for multicast lists, and (b) improves commonality
    of code between the "destroy one" and "destroy all" paths by performing
    final free activity via destructor instead of explicitly (and differently)
    in each path.
    
    "Sean E. Millichamp" <sean@...enor.org> reported the workqueue
    leak, and included a different patch.
    
    Signed-off-by: Jay Vosburgh <fubar@...ibm.com>
    Signed-off-by: Jeff Garzik <jgarzik@...hat.com>


	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html