From: Corey Hickey <bugfood-ml@fatooh.org>
To: Patrick McHardy <kaber@trash.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH 2/7] Preparatory refactoring part 2.
Date: Tue, 31 Jul 2007 00:43:43 -0700 [thread overview]
Message-ID: <46AEE82F.5040603@fatooh.org> (raw)
In-Reply-To: <46ADEEC5.9030600@trash.net>
Patrick McHardy wrote:
> Corey Hickey wrote:
>> diff --git a/net/sched/sch_sfq.c b/net/sched/sch_sfq.c
>> index 8ae077f..0c46938 100644
>> --- a/net/sched/sch_sfq.c
>> +++ b/net/sched/sch_sfq.c
>> @@ -380,71 +380,71 @@ static void sfq_perturbation(unsigned long arg)
>> }
>> }
>>
>> -static int sfq_change(struct Qdisc *sch, struct rtattr *opt)
>> +static int sfq_q_init(struct sfq_sched_data *q, struct rtattr *opt)
>> {
>> - struct sfq_sched_data *q = qdisc_priv(sch);
>> struct tc_sfq_qopt *ctl = RTA_DATA(opt);
>> - unsigned int qlen;
>> + int i;
>>
>> - if (opt->rta_len < RTA_LENGTH(sizeof(*ctl)))
>> + if (opt && opt->rta_len < RTA_LENGTH(sizeof(*ctl)))
>
>
> opt is dereferenced above (RTA_DATA), so if it is NULL we've already
> crashed.
I think that test made ESFQ not crash when I did a "qdisc change"
without giving any parameters, but that was a while ago and I might be
mistaken. I'll need to rewrite much of this function anyway, and I'll
pay attention to what happens when I get there.
>> return -EINVAL;
>>
>> - sch_tree_lock(sch);
>> - q->quantum = ctl->quantum ? : psched_mtu(sch->dev);
>> - q->perturb_period = ctl->perturb_period*HZ;
>> - if (ctl->limit)
>> - q->limit = min_t(u32, ctl->limit, SFQ_DEPTH);
>> + q->perturbation = 0;
>> + q->max_depth = 0;
>> + q->tail = q->limit = SFQ_DEPTH;
>> + if (opt == NULL) {
>> + q->perturb_period = 0;
>> + } else {
>> + struct tc_sfq_qopt *ctl = RTA_DATA(opt);
>> + if (ctl->quantum)
>> + q->quantum = ctl->quantum;
>> + q->perturb_period = ctl->perturb_period*HZ;
>>
>> - qlen = sch->q.qlen;
>> - while (sch->q.qlen >= q->limit-1)
>> - sfq_drop(sch);
>> - qdisc_tree_decrease_qlen(sch, qlen - sch->q.qlen);
>
>
> I hope that patch that makes changing possible brings this back ..
> <checking> .. it doesn't. Please either keep this or fix up 6/7
> to bring it back.
It got lost in translation; I will add it to 6/7.
Thanks,
Corey
next prev parent reply other threads:[~2007-07-31 7:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 0:21 SFQ: backport some features from ESFQ (try 2) Corey Hickey
2007-07-30 0:21 ` [PATCH 1/7] Preparatory refactoring part 1 Corey Hickey
2007-07-30 13:51 ` Patrick McHardy
2007-07-31 1:26 ` Corey Hickey
2007-07-31 10:46 ` Patrick McHardy
2007-07-30 0:21 ` [PATCH 2/7] Preparatory refactoring part 2 Corey Hickey
2007-07-30 13:59 ` Patrick McHardy
2007-07-31 7:43 ` Corey Hickey [this message]
2007-07-30 0:21 ` [PATCH 3/7] Move two functions Corey Hickey
2007-07-30 0:21 ` [PATCH 4/7] Add "depth" Corey Hickey
2007-07-30 0:21 ` [PATCH 5/7] Add divisor Corey Hickey
2007-07-30 0:21 ` [PATCH 6/7] Make qdisc changeable Corey Hickey
2007-07-30 14:11 ` Patrick McHardy
2007-07-31 7:43 ` Corey Hickey
2007-08-06 2:47 ` Corey Hickey
2007-08-06 12:06 ` Patrick McHardy
2007-07-30 0:21 ` [PATCH 7/7] Remove comments about hardcoded values Corey Hickey
2007-07-30 0:21 ` [PATCH] [iproute2] SFQ: Support changing depth and divisor Corey Hickey
-- strict thread matches above, loose matches on Subject: below --
2007-07-29 7:08 [PATCH 0/7] SFQ: backport some features from ESFQ Corey Hickey
2007-07-29 7:08 ` [PATCH 1/7] Preparatory refactoring part 1 Corey Hickey
2007-07-29 7:08 ` [PATCH 2/7] Preparatory refactoring part 2 Corey Hickey
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=46AEE82F.5040603@fatooh.org \
--to=bugfood-ml@fatooh.org \
--cc=kaber@trash.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 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).