From: Tomas Szepe <szepe@pinerecords.com>
To: jamal <hadi@cyberus.ca>
Cc: Marc-Christian Petersen <m.c.p@wolk-project.de>,
Manfred Spraul <manfred@colorfullife.com>,
Catalin BOIE <util@deuroconsult.ro>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH] qdisc oops fix
Date: Wed, 16 Apr 2003 23:44:23 +0200 [thread overview]
Message-ID: <20030416214422.GM32575@louise.pinerecords.com> (raw)
In-Reply-To: <20030416140440.O5912@shell.cyberus.ca>
> [hadi@cyberus.ca]
> >
> > > >The original backtrace as provided by Martin Volf does not contain
> > > >any weird addresses such as 0xd081ecc7 above:
> > > >http://marc.theaimsgroup.com/?l=linux-kernel&m=105013596721774&w=2
> > > Thanks.
> > > The bug was caused by sch_tree_lock() in htb_change_class().
> > > 2.4.21-pre7 contains a fix.
> > am I just blind or isn't there a fix in -pre7|current-BK?
> >
>
> No you are not ;-> Yes, the fix for that specific problem is in
> 2.4.21-pre7. I think Tomas might have missed that we moved on to the
> next problem.
Trouble is, the fix went in for already -pre5 (cset 1.930.3.5), so if you
only look at the pre6->pre7 changelog (like I did), you aren't likely to
find it. 8)
T.
next prev parent reply other threads:[~2003-04-16 21:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 13:09 [PATCH] qdisc oops fix jamal
2003-04-15 13:43 ` Tomas Szepe
2003-04-15 14:31 ` jamal
2003-04-15 21:10 ` Tomas Szepe
2003-04-16 5:41 ` Catalin BOIE
2003-04-16 11:49 ` jamal
2003-04-16 15:23 ` Manfred Spraul
2003-04-16 16:06 ` Tomas Szepe
2003-04-16 16:52 ` Manfred Spraul
2003-04-16 18:03 ` Marc-Christian Petersen
2003-04-16 18:18 ` jamal
2003-04-16 21:44 ` Tomas Szepe [this message]
2003-04-17 5:25 ` Catalin BOIE
2003-04-16 18:39 ` jamal
2003-04-16 19:43 ` Julian Anastasov
2003-04-17 6:06 ` Catalin BOIE
2003-04-17 10:55 ` jamal
2003-04-18 6:47 ` Catalin BOIE
2003-04-17 5:13 ` Catalin BOIE
-- strict thread matches above, loose matches on Subject: below --
2003-04-15 22:42 Julian Anastasov
2003-04-16 0:53 ` jamal
2003-04-16 6:30 ` devik
2003-04-16 7:24 ` Julian Anastasov
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=20030416214422.GM32575@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=hadi@cyberus.ca \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=manfred@colorfullife.com \
--cc=netdev@oss.sgi.com \
--cc=util@deuroconsult.ro \
/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).