netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yuval Shaia <yuval.shaia@oracle.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, nicholashuber@gmail.com,
	labbott@redhat.com, Jamal Hadi Salim <jhs@mojatatu.com>
Subject: Re: [Patch net] net_sched: move tcf_lock down after gen_replace_estimator()
Date: Tue, 13 Jun 2017 23:40:41 +0300	[thread overview]
Message-ID: <20170613204040.GB3112@yuvallap> (raw)
In-Reply-To: <1497386184-14960-1-git-send-email-xiyou.wangcong@gmail.com>

On Tue, Jun 13, 2017 at 01:36:24PM -0700, Cong Wang wrote:
> Laura reported a sleep-in-atomic kernel warning inside

Since you added a Reported-by tag below i don't see a reason to
specifically mention it in commit log message.

> tcf_act_police_init() which calls gen_replace_estimator() with
> spinlock protection.
> 
> It is not necessary in this case, we already have RTNL lock here
> so it is enough to protect concurrent writers. For the reader,
> i.e. tcf_act_police(), it needs to make decision based on this
> rate estimator, in the worst case we drop more/less packets than
> necessary while changing the rate in parallel, it is still acceptable.
> 
> Reported-by: Laura Abbott <labbott@redhat.com>
> Reported-by: Nick Huber <nicholashuber@gmail.com>
> Cc: Jamal Hadi Salim <jhs@mojatatu.com>
> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
> ---
>  net/sched/act_police.c | 8 +++-----
>  1 file changed, 3 insertions(+), 5 deletions(-)
> 
> diff --git a/net/sched/act_police.c b/net/sched/act_police.c
> index f42008b..b062bc8 100644
> --- a/net/sched/act_police.c
> +++ b/net/sched/act_police.c
> @@ -132,21 +132,21 @@ static int tcf_act_police_init(struct net *net, struct nlattr *nla,
>  		}
>  	}
>  
> -	spin_lock_bh(&police->tcf_lock);
>  	if (est) {
>  		err = gen_replace_estimator(&police->tcf_bstats, NULL,
>  					    &police->tcf_rate_est,
>  					    &police->tcf_lock,
>  					    NULL, est);
>  		if (err)
> -			goto failure_unlock;
> +			goto failure;
>  	} else if (tb[TCA_POLICE_AVRATE] &&
>  		   (ret == ACT_P_CREATED ||
>  		    !gen_estimator_active(&police->tcf_rate_est))) {
>  		err = -EINVAL;
> -		goto failure_unlock;
> +		goto failure;
>  	}
>  
> +	spin_lock_bh(&police->tcf_lock);
>  	/* No failure allowed after this point */
>  	police->tcfp_mtu = parm->mtu;
>  	if (police->tcfp_mtu == 0) {
> @@ -192,8 +192,6 @@ static int tcf_act_police_init(struct net *net, struct nlattr *nla,
>  
>  	return ret;
>  
> -failure_unlock:
> -	spin_unlock_bh(&police->tcf_lock);
>  failure:
>  	qdisc_put_rtab(P_tab);
>  	qdisc_put_rtab(R_tab);
> -- 
> 2.5.5
> 

  reply	other threads:[~2017-06-13 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 20:36 [Patch net] net_sched: move tcf_lock down after gen_replace_estimator() Cong Wang
2017-06-13 20:40 ` Yuval Shaia [this message]
2017-06-13 20:45   ` Cong Wang
2017-06-14 18:42   ` David Miller
2017-06-14 12:48 ` Jamal Hadi Salim
2017-06-14 18:41 ` 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=20170613204040.GB3112@yuvallap \
    --to=yuval.shaia@oracle.com \
    --cc=jhs@mojatatu.com \
    --cc=labbott@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicholashuber@gmail.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).