lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080818104355.GB6548@ff.dom.local>
Date:	Mon, 18 Aug 2008 10:43:56 +0000
From:	Jarek Poplawski <jarkao2@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH]: Schedule correct qdisc in watchdog.

On Mon, Aug 18, 2008 at 10:35:59AM +0000, Jarek Poplawski wrote:
> On Mon, Aug 18, 2008 at 03:10:03AM -0700, David Miller wrote:
> > From: Jarek Poplawski <jarkao2@...il.com>
> > Date: Mon, 18 Aug 2008 09:47:27 +0000
> > 
> > > Maybe I wrote this wrong. wd->qdisc stores qdisc from the
> > > qdisc_watchdog_init() time, and this could be &noop_qdisc.
> > > So qdisc_root() would schedule wrong qdisc later. BTW, my
> > > version would probably do the same for root qdisc, but in
> > > these tests there was a problem with leafs.
> > 
> > qdisc_watchdog_init() is only invoked by:
> > 
> > net/sched/sch_cbq.c:	qdisc_watchdog_init(&q->watchdog, sch);
> > net/sched/sch_hfsc.c:	qdisc_watchdog_init(&q->watchdog, sch);
> > net/sched/sch_htb.c:	qdisc_watchdog_init(&q->watchdog, sch);
> > net/sched/sch_netem.c:	qdisc_watchdog_init(&q->watchdog, sch);
> > net/sched/sch_tbf.c:	qdisc_watchdog_init(&q->watchdog, sch);
> > 
> > These "q" things are the scheduler private structs, and 'sch' of the
> > qdisc type indicated by the source file the code in question resides
> > :-)
> > 
> > This watchdog is different from the TX timeout watchdog which is
> > implemented in net/sch/sch_generic.c, which you may be confusing this
> > qdisc_watchdog_init() one with.
> 
> I don't think I wrote anything which could suggest I confused these
> watchdogs.
> 
> > 
> > The watchdog we are discussing here is purely for qdiscs where time
> > based events modify qdisc state (such as making new quotas available
> > for a flow, thus making certain packets eligible for scheduling that
> > were not beforehand)
> > 
> > So really, it cannot be &noop_qdisc as far as I can see.
> > :-)
> 
> Sure, ->sch is never &noop_qdisc, but your qdisc_root(sch) most
> probably is at the moment of qdisc_watchdog_init(). My version
> can do the same if eg. htb is root qdisc because at the moment
> of qdisc_create() qdisc_sleeping could be &noop_qdisc as well.
> But, in case we have a qdisc_sleeping already, it should work.
> 
> So these patches will stop break things, but these qdisc_watchdog()
> calls would be sometimes/always useless.

Sooory!!! Forget this all: it looks like your patch is damn right!

Jarek P.

PS: I'm still sleeping...
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ