[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20141029.142934.1722309776700951536.davem@davemloft.net>
Date: Wed, 29 Oct 2014 14:29:34 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: xiyou.wangcong@...il.com
Cc: netdev@...r.kernel.org, wang.bo116@....com.cn,
john.r.fastabend@...el.com, edumazet@...gle.com, kaber@...sh.net,
vtlam@...gle.com
Subject: Re: [Patch net 2/2] net_sched: always call ->destroy when ->init()
fails
From: Cong Wang <xiyou.wangcong@...il.com>
Date: Fri, 24 Oct 2014 16:55:59 -0700
> In qdisc_create(), when ->init() exists and it fails, we should
> call ->destroy() to clean up the potentially partially initialized
> qdisc's. This will also make the ->init() implementation easier.
>
> qdisc_create_dflt() already does that. Most callers of qdisc_create_dflt()
> simply use noop_qdisc when it fails.
>
> And, most of the ->destroy() implementations are already able to clean up
> partially initialization, we don't need to worry.
>
> The following ->init()'s need to catch up:
> fq_codel_init(), hhf_init(), multiq_init(), sfq_init(), mq_init(),
> mqprio_init().
>
> Reported-by: Wang Bo <wang.bo116@....com.cn>
> Signed-off-by: Cong Wang <xiyou.wangcong@...il.com>
As discussed, I really want to see ->init() clean up it's own crap.
There are certain kinds of initializations that cannot be tested for,
such as setting up a workqueue etc.
Therefore, the mere idea that we can call ->destroy() to handle this
is a pure non-starter as far as I am concerned.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists