From: sandr8 <sandr8_NOSPAM_@crocetta.org>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com
Subject: should that bugfix wait till 2.6.9? {was Re: Big set of networking updates}
Date: Thu, 19 Aug 2004 15:57:58 +0200 [thread overview]
Message-ID: <4124B1E6.3060808@crocetta.org> (raw)
In-Reply-To: <20040818173736.7ad8e58a.davem@redhat.com>
David S. Miller wrote:
>ChangeSet@1.1845, 2004-08-15 19:33:16-07:00, kaber@trash.net
> [PKT_SCHED]: cacheline-align qdisc data in qdisc_create()
>
> Signed-off-by: Patrick McHardy <kaber@trash.net>
> Signed-off-by: David S. Miller <davem@redhat.com>
>
> net/sched/sch_api.c | 21 +++++++++++++--------
> 1 files changed, 13 insertions(+), 8 deletions(-)
>
>
i was just going to send a similar changeset, since i didn't see any
discussion so far about that...
this changeset fixes a bug that is in 2.6.8.1 and 2.6.8 as well. today i
fixed it on my own too, since it was messing up a lot of things...
the handling of the private data belonging to a qdisc was inconsistent.
the memory allocated was not the memory used and hence its content could
change.
even worst what happened with a qdisc that had a pointer in its private
data... god knows what was going on...
isn't it urgent that people patch their kernel? is it possible for them
to wait till 2.6.9? i had oops regarding ext3 before finding and
repairing that bug!
cheers
Alessandro
prev parent reply other threads:[~2004-08-19 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 0:37 Big set of networking updates David S. Miller
2004-08-19 12:15 ` Harald Welte
2004-08-19 14:27 ` David S. Miller
2004-08-19 13:57 ` sandr8 [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=4124B1E6.3060808@crocetta.org \
--to=sandr8_nospam_@crocetta.org \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
/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).