Re: Unlock in_ioctl_get(), push kernel lock into in_ioctl_{set,change}_ifaddr()

2023-04-14 Thread Klemens Nanni
On Sat, Dec 10, 2022 at 03:40:35AM +, Klemens Nanni wrote: > On Wed, Nov 30, 2022 at 06:17:51PM +, Klemens Nanni wrote: > > Follow up on how in6_ioctl() does it: grab the kernel lock in all the > > ioctl specific functions, where needed and not earlier, i.e. exactly where > > the net lock

Re: Unlock in_ioctl_get(), push kernel lock into in_ioctl_{set,change}_ifaddr()

2022-12-09 Thread Klemens Nanni
On Wed, Nov 30, 2022 at 06:17:51PM +, Klemens Nanni wrote: > Follow up on how in6_ioctl() does it: grab the kernel lock in all the > ioctl specific functions, where needed and not earlier, i.e. exactly where > the net lock is currently taken/released. > > Like in6_ioctl_get(), in_ioctl_get()

Unlock in_ioctl_get(), push kernel lock into in_ioctl_{set,change}_ifaddr()

2022-11-30 Thread Klemens Nanni
Follow up on how in6_ioctl() does it: grab the kernel lock in all the ioctl specific functions, where needed and not earlier, i.e. exactly where the net lock is currently taken/released. Like in6_ioctl_get(), in_ioctl_get() simply grabs a net lock protected interface address, may check net lock