search for: wpan4

...e is deleted later. > If you reproduced it, is the device later removed or is it really stuck? I ran the reproducer again without the patch and it seems you are correct. It was trying to create a very short-lived bridge, then delete it immediately in the next call. The device in question "wpan4" never showed up when I polled with `ip link` in the VM, so I'd say it did not get stuck. > How would it leak a reference, could you elaborate? > The reference is always taken and always released after the call. This was where I got a bit confused too. The system had a timeout of 1...

Hi Ziqi, On 8/19/23 11:10, Ziqi Zhao wrote: > In the bug reported by Syzbot, certain bridge devices would have a > leaked reference created by race conditions in dev_ioctl, specifically, > under SIOCBRADDIF or SIOCBRDELIF operations. The reference leak would How would it leak a reference, could you elaborate? The reference is always taken and always released after the call. > be

...;> If you reproduced it, is the device later removed or is it really stuck? > > I ran the reproducer again without the patch and it seems you are > correct. It was trying to create a very short-lived bridge, then delete > it immediately in the next call. The device in question "wpan4" never > showed up when I polled with `ip link` in the VM, so I'd say it did not > get stuck. > >> How would it leak a reference, could you elaborate? >> The reference is always taken and always released after the call. > > This was where I got a bit confused t...