[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180327.131826.868714983333063962.davem@davemloft.net>
Date: Tue, 27 Mar 2018 13:18:26 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: ktkhai@...tuozzo.com
Cc: nicolas.dichtel@...nd.com, vyasevic@...hat.com,
paulmck@...ux.vnet.ibm.com, vyasevich@...il.com,
mark.rutland@....com, leonro@...lanox.com, avagin@...tuozzo.com,
fw@...len.de, ebiederm@...ssion.com, roman.kapl@...go.com,
dsahern@...il.com, netdev@...r.kernel.org, bfields@...ldses.org
Subject: Re: [PATCH net-next 0/5] Make pernet_operations always read locked
From: Kirill Tkhai <ktkhai@...tuozzo.com>
Date: Tue, 27 Mar 2018 18:01:42 +0300
> All the pernet_operations are converted, and the last one
> is in this patchset (nfsd_net_ops acked by J. Bruce Fields).
> So, it's the time to kill pernet_operations::async field,
> and make setup_net() and cleanup_net() always require
> the rwsem only read locked.
>
> All further pernet_operations have to be developed to fit
> this rule. Some of previous patches added a comment to
> struct pernet_operations about that.
>
> Also, this patchset renames net_sem to pernet_ops_rwsem
> to make the target area of the rwsem is more clear visible,
> and adds more comments.
Amazing work, series applied, thanks!
Powered by blists - more mailing lists