From: Cong Wang <xiyou.wangcong@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Simon Horman <simon.horman@netronome.com>,
john.hurley@netronome.com, David Ahern <dsahern@gmail.com>,
mlxsw@mellanox.com, sridhar.samudrala@intel.com
Subject: Re: [patch net-next v4 03/12] net: sched: introduce chain object to uapi
Date: Tue, 24 Jul 2018 16:20:08 -0700 [thread overview]
Message-ID: <CAM_iQpXxOOAw06tGiCmkWrMkU4xoNO8cwTP349vU8AGj--OXVQ@mail.gmail.com> (raw)
In-Reply-To: <CAM_iQpU41g_aSd7wbRk5r+hbVRdoDYnLWANjOJtZYgf4qfx0_w@mail.gmail.com>
On Tue, Jul 24, 2018 at 3:30 PM Cong Wang <xiyou.wangcong@gmail.com> wrote:
>
> On Mon, Jul 23, 2018 at 12:25 AM Jiri Pirko <jiri@resnulli.us> wrote:
> > + switch (n->nlmsg_type) {
> > + case RTM_NEWCHAIN:
> > + /* In case the chain was successfully added, take a reference
> > + * to the chain. This ensures that an empty chain
> > + * does not disappear at the end of this function.
> > + */
> > + tcf_chain_hold(chain);
> > + chain->explicitly_created = true;
> > + tc_chain_notify(chain, NULL, 0, NLM_F_CREATE | NLM_F_EXCL,
> > + RTM_NEWCHAIN, false);
> > + break;
> > + case RTM_DELCHAIN:
> > + /* Flush the chain first as the user requested chain removal. */
> > + tcf_chain_flush(chain);
> > + /* In case the chain was successfully deleted, put a reference
> > + * to the chain previously taken during addition.
> > + */
> > + tcf_chain_put_explicitly_created(chain);
> > + break;
>
> I don't see you send notification to user-space when deleting a chain,
> am I missing anything?
Oh, it is hidden in tcf_chain_put():
void tcf_chain_put(struct tcf_chain *chain)
{
if (--chain->refcnt == 0) {
tc_chain_notify(chain, NULL, 0, 0, RTM_DELCHAIN, false);
tc_chain_tmplt_del(chain);
tcf_chain_destroy(chain);
}
}
So, you only send out notification when the last refcnt is gone.
If the chain that is being deleted by a user is still used by an action,
you return 0 or -EPERM?
next prev parent reply other threads:[~2018-07-25 0:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 7:23 [patch net-next v4 00/12] sched: introduce chain templates support with offloading to mlxsw Jiri Pirko
2018-07-23 7:23 ` [patch net-next v4 01/12] net: sched: push ops lookup bits into tcf_proto_lookup_ops() Jiri Pirko
2018-07-23 7:23 ` [patch net-next v4 02/12] net: sched: Avoid implicit chain 0 creation Jiri Pirko
2018-07-23 7:23 ` [patch net-next v4 03/12] net: sched: introduce chain object to uapi Jiri Pirko
2018-07-24 22:30 ` Cong Wang
2018-07-24 23:20 ` Cong Wang [this message]
2018-07-25 6:46 ` Jiri Pirko
2018-07-25 16:40 ` Cong Wang
2018-07-26 7:38 ` Jiri Pirko
2018-07-26 10:06 ` Jiri Pirko
2018-07-26 12:27 ` Jiri Pirko
2018-07-23 7:23 ` [patch net-next v4 04/12] net: sched: introduce chain templates Jiri Pirko
2018-07-23 7:23 ` [patch net-next v4 05/12] net: sched: cls_flower: move key/mask dumping into a separate function Jiri Pirko
2018-07-23 7:23 ` [patch net-next v4 06/12] net: sched: cls_flower: change fl_init_dissector to accept mask and dissector Jiri Pirko
2018-07-23 7:23 ` [patch net-next v4 07/12] net: sched: cls_flower: implement chain templates Jiri Pirko
2018-07-23 7:23 ` [patch net-next v4 08/12] net: sched: cls_flower: propagate chain teplate creation and destruction to drivers Jiri Pirko
2018-07-23 7:23 ` [patch net-next v4 09/12] mlxsw: spectrum: Implement chain template hinting Jiri Pirko
2018-07-23 7:24 ` [patch net-next v4 10/12] selftests: forwarding: move shblock tc support check to a separate helper Jiri Pirko
2018-07-23 7:24 ` [patch net-next v4 11/12] selftests: forwarding: add tests for TC chains creation adn destruction Jiri Pirko
2018-07-23 7:24 ` [patch net-next v4 12/12] selftests: forwarding: add tests for TC chain templates Jiri Pirko
2018-07-23 7:24 ` [patch iproute2/net-next v4] tc: introduce support for " Jiri Pirko
2018-07-25 17:03 ` David Ahern
2018-07-23 16:28 ` [patch net-next v4 00/12] sched: introduce chain templates support with offloading to mlxsw David Miller
2018-07-23 23:36 ` Jakub Kicinski
2018-07-24 3:45 ` David Miller
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=CAM_iQpXxOOAw06tGiCmkWrMkU4xoNO8cwTP349vU8AGj--OXVQ@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.hurley@netronome.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.com \
--cc=sridhar.samudrala@intel.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;
as well as URLs for NNTP newsgroup(s).