lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iL=-V=f4Kzdi-AdrLXQzLYLi_=nz7eW7tWN-=1XrWnEHQ@mail.gmail.com>
Date: Thu, 8 Feb 2024 12:53:38 +0100
From: Eric Dumazet <edumazet@...gle.com>
To: "David S . Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, 
	Paolo Abeni <pabeni@...hat.com>
Cc: David Ahern <dsahern@...nel.org>, netdev@...r.kernel.org, eric.dumazet@...il.com
Subject: Re: [PATCH net-next 3/4] ipmr: use exit_batch_rtnl method

On Thu, Feb 8, 2024 at 12:16 PM Eric Dumazet <edumazet@...gle.com> wrote:
>
> Using exit_batch_rtnl method instead of exit_batch avoids
> one rtnl_lock()/rtnl_unlock() pair in netns dismantle.
>



>
>  static struct pernet_operations ipmr_net_ops = {
>         .init = ipmr_net_init,
>         .exit = ipmr_net_exit,
> -       .exit_batch = ipmr_net_exit_batch,
> +       .exit_batch = ipmr_exit_batch_rtnl,
>  };

Oh well, I thought I fixed this error, I must have missed a step.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ