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
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()
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