From: David Miller <davem@davemloft.net>
To: ktkhai@virtuozzo.com
Cc: nicolas.dichtel@6wind.com, vyasevic@redhat.com,
paulmck@linux.vnet.ibm.com, vyasevich@gmail.com,
mark.rutland@arm.com, leonro@mellanox.com, avagin@virtuozzo.com,
fw@strlen.de, ebiederm@xmission.com, roman.kapl@sysgo.com,
dsahern@gmail.com, netdev@vger.kernel.org, bfields@fieldses.org
Subject: Re: [PATCH net-next 0/5] Make pernet_operations always read locked
Date: Tue, 27 Mar 2018 13:18:26 -0400 (EDT) [thread overview]
Message-ID: <20180327.131826.868714983333063962.davem@davemloft.net> (raw)
In-Reply-To: <152216238129.1634.4807322431520445566.stgit@localhost.localdomain>
From: Kirill Tkhai <ktkhai@virtuozzo.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!
next prev parent reply other threads:[~2018-03-27 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 15:01 [PATCH net-next 0/5] Make pernet_operations always read locked Kirill Tkhai
2018-03-27 15:01 ` [PATCH net-next 1/5] net: Convert nfsd_net_ops Kirill Tkhai
2018-03-27 15:02 ` [PATCH net-next 2/5] net: Reflect all pernet_operations are converted Kirill Tkhai
2018-03-27 15:02 ` [PATCH net-next 3/5] net: Drop pernet_operations::async Kirill Tkhai
2018-03-27 15:02 ` [PATCH net-next 4/5] net: Rename net_sem to pernet_ops_rwsem Kirill Tkhai
2018-03-27 15:02 ` [PATCH net-next 5/5] net: Add more comments Kirill Tkhai
2018-03-27 17:18 ` David Miller [this message]
2018-03-27 17:34 ` [PATCH net-next 0/5] Make pernet_operations always read locked Kirill Tkhai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180327.131826.868714983333063962.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=avagin@virtuozzo.com \
--cc=bfields@fieldses.org \
--cc=dsahern@gmail.com \
--cc=ebiederm@xmission.com \
--cc=fw@strlen.de \
--cc=ktkhai@virtuozzo.com \
--cc=leonro@mellanox.com \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=roman.kapl@sysgo.com \
--cc=vyasevic@redhat.com \
--cc=vyasevich@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox