From: David Miller <davem@davemloft.net>
To: john.fastabend@gmail.com
Cc: xiyou.wangcong@gmail.com, jhs@mojatatu.com,
eric.dumazet@gmail.com, netdev@vger.kernel.org,
paulmck@linux.vnet.ibm.com, brouer@redhat.com
Subject: Re: [net-next PATCH v2 02/15] net: rcu-ify tcf_proto
Date: Tue, 02 Sep 2014 13:52:18 -0700 (PDT) [thread overview]
Message-ID: <20140902.135218.623659943093020151.davem@davemloft.net> (raw)
In-Reply-To: <54051FC1.6030106@gmail.com>
From: John Fastabend <john.fastabend@gmail.com>
Date: Mon, 01 Sep 2014 18:39:13 -0700
> On 08/24/2014 10:31 PM, David Miller wrote:
>> From: John Fastabend <john.fastabend@gmail.com>
>> Date: Sun, 24 Aug 2014 17:48:31 -0700
>>
>>> @@ -722,8 +724,9 @@ static void sfq_free(void *addr)
>>> static void sfq_destroy(struct Qdisc *sch)
>>> {
>>> struct sfq_sched_data *q = qdisc_priv(sch);
>>> + struct tcf_proto *fl = rtnl_dereference(q->filter_list);
>>>
>>> - tcf_destroy_chain(&q->filter_list);
>>> + tcf_destroy_chain(&fl);
>
> Sorry for the delayed reply...
>
>>
>> This will cause tcf_destroy_chain() to set the local variable
>> 'fl' to NULL rather than q->filter_list.
>>
>> I don't see how this can be correct at all.
>
> Right now (without these patches) nothing sets q->filter_list
> to NULL and we only call this when the qdisc is being destroyed.
Yes, it does set it to NULL, by virtue of how the loop iterates.
It iterates by setting the "*fl" to tp->next until that evaluates to
NULL. Thereby setting *fl to NULL.
So the old code would set ->filter_list to NULL, your code will not.
next prev parent reply other threads:[~2014-09-02 20:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 0:47 [net-next PATCH v2 00/15] net/sched: use rcu filters John Fastabend
2014-08-25 0:48 ` [net-next PATCH v2 01/15] net: qdisc: use rcu prefix and silence sparse warnings John Fastabend
2014-08-25 0:48 ` [net-next PATCH v2 02/15] net: rcu-ify tcf_proto John Fastabend
2014-08-25 5:31 ` David Miller
2014-09-02 1:39 ` John Fastabend
2014-09-02 20:52 ` David Miller [this message]
2014-09-03 6:23 ` John Fastabend
2014-08-25 0:49 ` [net-next PATCH v2 03/15] net: sched: cls_basic use RCU John Fastabend
2014-08-25 0:49 ` [net-next PATCH v2 04/15] net: sched: cls_cgroup " John Fastabend
2014-08-25 0:49 ` [net-next PATCH v2 05/15] net: sched: cls_flow " John Fastabend
2014-08-25 0:50 ` [net-next PATCH v2 06/15] net: sched: fw " John Fastabend
2014-08-25 0:50 ` [net-next PATCH v2 07/15] net: sched: RCU cls_route John Fastabend
2014-08-25 0:51 ` [net-next PATCH v2 08/15] net: sched: RCU cls_tcindex John Fastabend
2014-08-25 0:51 ` [net-next PATCH v2 09/15] net: sched: make cls_u32 lockless John Fastabend
2014-08-25 0:52 ` [net-next PATCH v2 10/15] net: sched: rcu'ify cls_rsvp John Fastabend
2014-08-25 0:52 ` [net-next PATCH v2 11/15] net: sched: rcu'ify cls_bpf John Fastabend
2014-08-25 0:53 ` [net-next PATCH v2 12/15] net: sched: make tc_action safe to walk under RCU John Fastabend
2014-08-25 0:53 ` [net-next PATCH v2 13/15] net: sched: make bstats per cpu and estimator RCU safe John Fastabend
2014-08-25 0:53 ` [net-next PATCH v2 14/15] net: sched: make qstats per cpu John Fastabend
2014-08-25 0:54 ` [net-next PATCH v2 15/15] net: sched: drop ingress qdisc lock John Fastabend
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=20140902.135218.623659943093020151.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brouer@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=xiyou.wangcong@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;
as well as URLs for NNTP newsgroup(s).