All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@vger.kernel.org, "David S\. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 2.6.19-rc4-git10][PKT_SCHED] sch_htb: INIT_HLIST_NODE after hlist_del()
Date: Wed, 8 Nov 2006 07:36:45 +0100	[thread overview]
Message-ID: <20061108063645.GA984@ff.dom.local> (raw)
In-Reply-To: <20061107095007.71c11b47@freekitty>

On Tue, Nov 07, 2006 at 09:50:07AM -0800, Stephen Hemminger wrote:
> On Tue, 7 Nov 2006 07:49:43 +0100
> Jarek Poplawski <jarkao2@o2.pl> wrote:
...
> Your patch duplicated the code in hlist_del_init().  Why not do:
> 
> --- a/net/sched/sch_htb.c	2006-11-07 09:48:22.000000000 -0800
> +++ b/net/sched/sch_htb.c	2006-11-07 09:49:01.000000000 -0800
> @@ -1284,8 +1284,7 @@
>  						  struct htb_class, sibling));
>  
>  	/* note: this delete may happen twice (see htb_delete) */
> -	if (!hlist_unhashed(&cl->hlist))
> -		hlist_del(&cl->hlist);
> +	hlist_del_init(&cl->hlist);
>  	list_del(&cl->sibling);
>  
>  	if (cl->prio_activity)
> @@ -1333,8 +1332,7 @@
>  	sch_tree_lock(sch);
>  
>  	/* delete from hash and active; remainder in destroy_class */
> -	if (!hlist_unhashed(&cl->hlist))
> -		hlist_del(&cl->hlist);
> +	hlist_del_init(&cl->hlist);
>  
>  	if (cl->prio_activity)
>  		htb_deactivate(q, cl);
> 

I've understood you first suggestion. But after sending
my patch I've found it is also hiding a real problem
of excessive deletion in one and possibly more places.
So probably this should be done the right way and this
hlist_unhashed testing left in BUG_ON only... 

Cheers,
Jarek P. 

      parent reply	other threads:[~2006-11-08  6:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 11:33 [PATCH 2.6.19-rc4-git10][PKT_SCHED] sch_htb: INIT_HLIST_NODE after hlist_del() Jarek Poplawski
2006-11-06 17:44 ` Stephen Hemminger
2006-11-07  6:49   ` Jarek Poplawski
2006-11-07 17:50     ` Stephen Hemminger
2006-11-07 22:55       ` David Miller
2006-11-08  6:36       ` Jarek Poplawski [this message]

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=20061108063645.GA984@ff.dom.local \
    --to=jarkao2@o2.pl \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.