From: David Miller <davem@davemloft.net>
To: david.ward@ll.mit.edu
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net_sched: gred: Fix oops in gred_dump() in WRED mode
Date: Mon, 16 Apr 2012 23:51:40 -0400 (EDT) [thread overview]
Message-ID: <20120416.235140.66658470499784164.davem@davemloft.net> (raw)
In-Reply-To: <1334529106-5035-1-git-send-email-david.ward@ll.mit.edu>
From: David Ward <david.ward@ll.mit.edu>
Date: Sun, 15 Apr 2012 18:31:45 -0400
> A parameter set exists for WRED mode, called wred_set, to hold the same
> values for qavg and qidlestart across all VQs. The WRED mode values had
> been previously held in the VQ for the default DP. After these values
> were moved to wred_set, the VQ for the default DP was no longer created
> automatically (so that it could be omitted on purpose, to have packets
> in the default DP enqueued directly to the device without using RED).
>
> However, gred_dump() was overlooked during that change; in WRED mode it
> still reads qavg/qidlestart from the VQ for the default DP, which might
> not even exist. As a result, this command sequence will cause an oops:
>
> tc qdisc add dev $DEV handle $HANDLE parent $PARENT gred setup \
> DPs 3 default 2 grio
> tc qdisc change dev $DEV handle $HANDLE gred DP 0 prio 8 $RED_OPTIONS
> tc qdisc change dev $DEV handle $HANDLE gred DP 1 prio 8 $RED_OPTIONS
>
> This fixes gred_dump() in WRED mode to use the values held in wred_set.
>
> Signed-off-by: David Ward <david.ward@ll.mit.edu>
Applied and queued up for -stable, thanks David.
prev parent reply other threads:[~2012-04-17 3:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 22:31 [PATCH] net_sched: gred: Fix oops in gred_dump() in WRED mode David Ward
2012-04-15 22:31 ` [PATCH] net_sched: red: Make minor corrections to comments David Ward
2012-04-16 13:06 ` Ward, David - 0663 - MITLL
2012-04-16 13:17 ` [PATCH v2] " David Ward
2012-04-17 3:53 ` David Miller
2012-04-17 3:51 ` David Miller [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=20120416.235140.66658470499784164.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david.ward@ll.mit.edu \
--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 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).