Netdev List
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [Patch net-next] net_sched: properly check for empty skb array on error path
Date: Mon, 18 Dec 2017 19:58:44 -0800	[thread overview]
Message-ID: <4caae5f5-63e2-65c8-522e-0dfe736a7738@gmail.com> (raw)
In-Reply-To: <CAM_iQpUVmrX9WvQjiT_cy74FWCJv-xGosLNNyuFGL8oGev+E1A@mail.gmail.com>

On 12/18/2017 06:20 PM, Cong Wang wrote:
> On Mon, Dec 18, 2017 at 5:25 PM, John Fastabend
> <john.fastabend@gmail.com> wrote:
>> On 12/18/2017 02:34 PM, Cong Wang wrote:
>>> First, the check of &q->ring.queue against NULL is wrong, it
>>> is always false. We should check the value rather than the address.
>>>
>>
>> Thanks.
>>
>>> Secondly, we need the same check in pfifo_fast_reset() too,
>>> as both ->reset() and ->destroy() are called in qdisc_destroy().
>>>
>>
>> not that it hurts to have the check here, but if init fails
>> in qdisc_create it seems only ->destroy() is called without
>> a ->reset().
>>
>> Is there another path for init() to fail that I'm missing.
> 
> Pretty sure ->reset() is called in qdisc_destroy() and also before
> ->destroy():
> 

Except, the failed init path does not call qdisc_destroy.

static struct Qdisc *qdisc_create(struct net_device *dev,
[...]

        if (ops->init) {
                err = ops->init(sch, tca[TCA_OPTIONS]);
                if (err != 0)
                        goto err_out5;
        }
[...]

err_out5:
        /* ops->init() failed, we call ->destroy() like qdisc_create_dflt() */
        if (ops->destroy)
                ops->destroy(sch);
err_out3:
        dev_put(dev);
        kfree((char *) sch - sch->padded);
err_out2:
        module_put(ops->owner);
err_out:
        *errp = err;
        return NULL;
[...]



> 
> void qdisc_destroy(struct Qdisc *qdisc)
> {
>         const struct Qdisc_ops  *ops = qdisc->ops;
>         struct sk_buff *skb, *tmp;
> 
>         if (qdisc->flags & TCQ_F_BUILTIN ||
>             !refcount_dec_and_test(&qdisc->refcnt))
>                 return;
> 
> #ifdef CONFIG_NET_SCHED
>         qdisc_hash_del(qdisc);
> 
>         qdisc_put_stab(rtnl_dereference(qdisc->stab));
> #endif
>         gen_kill_estimator(&qdisc->rate_est);
>         if (ops->reset)
>                 ops->reset(qdisc);
>         if (ops->destroy)
>                 ops->destroy(qdisc);
> 

  reply	other threads:[~2017-12-19  3:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 22:34 [Patch net-next] net_sched: properly check for empty skb array on error path Cong Wang
2017-12-19  1:25 ` John Fastabend
2017-12-19  2:20   ` Cong Wang
2017-12-19  3:58     ` John Fastabend [this message]
2017-12-19  4:31       ` Cong Wang
2017-12-19  4:54         ` John Fastabend
2017-12-19 19:13 ` 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=4caae5f5-63e2-65c8-522e-0dfe736a7738@gmail.com \
    --to=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --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