All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ismail Donmez <ismail@pardus.org.tr>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: 2.6.19 status
Date: Fri, 29 Sep 2006 10:10:34 +0300	[thread overview]
Message-ID: <200609291010.35025.ismail@pardus.org.tr> (raw)
In-Reply-To: <20060928.184135.41635707.davem@davemloft.net>

Hi Dave,
29 Eyl 2006 Cum 04:41 tarihinde şunları yazmıştınız:
> I've just pushed my current net-2.6 tree to Linus.  The bulk of the
> changes in there are endianness annotations for sparse by Al Viro,
> along with the patches I've been ACK'ing here on the list and
> elsewhere.
>
> If you want a non-bugfix change to get into 2.6.19 you must have it to
> me by the end of the weekend.
>
> As of next Monday, anything I receive has to be a bugfix for 2.6.19
> consideration.
>
> Thanks for everyone's hard work and let's make sure there are no
> networking regressions at all in 2.6.19, in fact let's strive to
> make it have no regressions plus bugs fixed that were in 2.6.18 :-)

Looks like following fix from Herbert still didn't made it to Linus which 
fixes hard lockups with some tc usage.


[NET_SCHED]: HTB: fix incorrect use of RB_EMPTY_NODE

Fix incorrect use of RB_EMPTY_NODE in htb_safe_rb_erase, which makes it
skip nodes within the rbtree instead of nodes not in the tree, resulting
in crashes later on.

The root cause for this seems to be the very counter-intuitive behaviour
of the RB_EMPTY_NODE macro, which returns _false_ when the node is empty.

Signed-off-by: Patrick McHardy <kaber@trash.net>

---
commit 9a0cd6d60280d88c38791844c87548d45cf6f2c2
tree fdf4f4a46fb088d957322006828af557b8ce594a
parent 7e4720201ad44ace85a443f41d668a62a737e7d0
author Patrick McHardy <kaber@trash.net> Wed, 27 Sep 2006 13:27:24 +0200
committer Patrick McHardy <kaber@trash.net> Wed, 27 Sep 2006 13:27:24 +0200

 net/sched/sch_htb.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/net/sched/sch_htb.c b/net/sched/sch_htb.c
index bb3ddd4..6c058e3 100644
--- a/net/sched/sch_htb.c
+++ b/net/sched/sch_htb.c
@@ -391,7 +391,7 @@ static inline void htb_add_class_to_row(
 /* If this triggers, it is a bug in this code, but it need not be fatal */
 static void htb_safe_rb_erase(struct rb_node *rb, struct rb_root *root)
 {
-	if (RB_EMPTY_NODE(rb)) {
+	if (!RB_EMPTY_NODE(rb)) {
 		WARN_ON(1);
 	} else {
 		rb_erase(rb, root);


-- 
They that can give up essential liberty to obtain a little temporary safety 
deserve neither liberty nor safety.
-- Benjamin Franklin

  reply	other threads:[~2006-09-29  7:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29  1:41 2.6.19 status David Miller
2006-09-29  7:10 ` Ismail Donmez [this message]
2006-09-29  7:48   ` 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=200609291010.35025.ismail@pardus.org.tr \
    --to=ismail@pardus.org.tr \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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.