Re: [libvirt] [PATCH 3/2] network: check newDef for used bridge names in addition to def

2015-04-27 Thread Shivaprasad bhat
On Sat, Apr 25, 2015 at 12:14 AM, Laine Stump la...@laine.org wrote: If someone has updated a network to change its bridge name, but the network is still active (so that bridge name hasn't taken effect yet), we still want to disallow another network from taking that new name. --- As suggested

Re: [libvirt] [PATCH 3/2] network: check newDef for used bridge names in addition to def

2015-04-27 Thread Shivaprasad bhat
On Mon, Apr 27, 2015 at 11:20 PM, Laine Stump la...@laine.org wrote: On 04/27/2015 05:54 AM, Shivaprasad bhat wrote: On Sat, Apr 25, 2015 at 12:14 AM, Laine Stump la...@laine.org wrote: If someone has updated a network to change its bridge name, but the network is still active (so that bridge

Re: [libvirt] [PATCH 3/2] network: check newDef for used bridge names in addition to def

2015-04-27 Thread Laine Stump
On 04/27/2015 05:54 AM, Shivaprasad bhat wrote: On Sat, Apr 25, 2015 at 12:14 AM, Laine Stump la...@laine.org wrote: If someone has updated a network to change its bridge name, but the network is still active (so that bridge name hasn't taken effect yet), we still want to disallow another

[libvirt] [PATCH 3/2] network: check newDef for used bridge names in addition to def

2015-04-24 Thread Laine Stump
If someone has updated a network to change its bridge name, but the network is still active (so that bridge name hasn't taken effect yet), we still want to disallow another network from taking that new name. --- As suggested by Shivaprasad following his tests of patches 1 and 2...