[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BB44BAC.2070304@redhat.com>
Date: Thu, 01 Apr 2010 15:30:52 +0800
From: Cong Wang <amwang@...hat.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
CC: linux-kernel@...r.kernel.org, Jiri Pirko <jpirko@...hat.com>,
Stephen Hemminger <shemminger@...tta.com>,
netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
bonding-devel@...ts.sourceforge.net,
Jay Vosburgh <fubar@...ibm.com>
Subject: [Patch V3] bonding: fix potential deadlock in bond_uninit()
Eric W. Biederman wrote:
> Amerigo Wang <amwang@...hat.com> writes:
>
>> bond_uninit() is invoked with rtnl_lock held, when it does destroy_workqueue()
>> which will potentially flush all works in this workqueue, if we hold rtnl_lock
>> again in the work function, it will deadlock.
>>
>> So move destroy_workqueue() to destructor where rtnl_lock is not held any more,
>> suggested by Eric.
>
> The error handling on creating a bond device needs to be updated as well.
>
Done.
View attachment "drivers-net-bonding-bond_main_c-fix-destroy_workqueue-deadlock.diff" of type "text/x-patch" (2518 bytes)
Powered by blists - more mailing lists