All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH]: Schedule correct qdisc in watchdog.
Date: Mon, 18 Aug 2008 09:10:12 +0000	[thread overview]
Message-ID: <20080818091011.GC5434@ff.dom.local> (raw)
In-Reply-To: <20080818.013954.187452037.davem@davemloft.net>

On Mon, Aug 18, 2008 at 01:39:54AM -0700, David Miller wrote:
> 
> Jarek, I bet this is what was causing the crash you were trying to fix
> yesterday.
> 
> But that's just my newbie hunch :-)

Yes, this was one of the reasons, but not the only one, and my oldbie
version of this fix could be found here as "02-fix1.patch":

http://permalink.gmane.org/gmane.linux.network/103039

It's a bit different, because I think wd->qdisc can probably
point to the noop_qdisc (if it's the root qdisc).

Anyway this kind of change is necessary here, and everywhere where
netif_schedule() could be called (I've found sch_cbq.c only).

Jarek P.

> 
> pkt_sched: Never scheduler non-root qdiscs.
> 
> The qdisc watchdogs can be attached to any qdisc,
> not just the root, so make sure we schedule the
> correct one.
> 
> Signed-off-by: David S. Miller <davem@davemloft.net>
> 
> diff --git a/net/sched/sch_api.c b/net/sched/sch_api.c
> index c8dc72e..98c0084 100644
> --- a/net/sched/sch_api.c
> +++ b/net/sched/sch_api.c
> @@ -426,7 +426,7 @@ static enum hrtimer_restart qdisc_watchdog(struct hrtimer *timer)
>  
>  	wd->qdisc->flags &= ~TCQ_F_THROTTLED;
>  	smp_wmb();
> -	__netif_schedule(wd->qdisc);
> +	__netif_schedule(qdisc_root(wd->qdisc));
>  
>  	return HRTIMER_NORESTART;
>  }

  reply	other threads:[~2008-08-18  9:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18  8:39 [PATCH]: Schedule correct qdisc in watchdog David Miller
2008-08-18  9:10 ` Jarek Poplawski [this message]
2008-08-18  9:31   ` David Miller
2008-08-18  9:47     ` Jarek Poplawski
2008-08-18 10:10       ` David Miller
2008-08-18 10:35         ` Jarek Poplawski
2008-08-18 10:43           ` Jarek Poplawski
2008-08-18 11:04             ` Denys Fedoryshchenko
2008-08-18 11:20               ` Jarek Poplawski
2008-08-18 11:35                 ` Jarek Poplawski
2008-08-18 12:45                   ` Denys Fedoryshchenko
2008-08-18 12:58                     ` Jarek Poplawski
2008-08-18 23:56                       ` David Miller
2008-08-19  5:37                         ` Jarek Poplawski
2008-08-19  5:39                           ` David Miller
2008-08-19  5:42                           ` Jarek Poplawski
2008-08-18 15:55                     ` Jarek Poplawski
2008-08-18 18:05                       ` Denys Fedoryshchenko
2008-08-19  3:54                   ` David Miller
2008-08-19  6:59                     ` Jarek Poplawski
2008-08-19  7:03                       ` David Miller
2008-08-18 11:06             ` Jarek Poplawski
2008-08-19  3:51               ` David Miller
2008-08-19  4:08                 ` 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=20080818091011.GC5434@ff.dom.local \
    --to=jarkao2@gmail.com \
    --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.