Messages in this thread | | | Date | Tue, 01 Sep 2020 13:01:27 -0700 (PDT) | Subject | Re: [PATCH] veth: fix memory leak in veth_newlink() | From | David Miller <> |
| |
From: Rustam Kovhaev <rkovhaev@gmail.com> Date: Sun, 30 Aug 2020 06:13:36 -0700
> when register_netdevice(dev) fails we should check whether struct > veth_rq has been allocated via ndo_init callback and free it, because, > depending on the code path, register_netdevice() might not call > priv_destructor() callback > > Reported-and-tested-by: syzbot+59ef240dd8f0ed7598a8@syzkaller.appspotmail.com > Link: https://syzkaller.appspot.com/bug?extid=59ef240dd8f0ed7598a8 > Signed-off-by: Rustam Kovhaev <rkovhaev@gmail.com>
I think I agree with Toshiaki here. There is no reason why the rollback_registered() path of register_netdevice() should behave differently from the normal control flow.
Any code path that invokes ->ndo_uninit() should probably also invoke the priv destructor.
The question is why does the err_uninit: label of register_netdevice behave differently from rollback_registered()? If there is a reason, it should be documented in a comment or similar. If it is wrong, it should be corrected.
| |