From: "David S. Miller" <davem@davemloft.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: kaber@trash.net, kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: [PATCH 2.6 NET] Fixes slab corruption in cbq_destroy
Date: Thu, 16 Sep 2004 13:29:23 -0700 [thread overview]
Message-ID: <20040916132923.0ac971f8.davem@davemloft.net> (raw)
In-Reply-To: <20040916132856.GA27293@postel.suug.ch>
On Thu, 16 Sep 2004 15:28:56 +0200
Thomas Graf <tgraf@suug.ch> wrote:
> Fixes slab corruption in cbq_destroy. cbq_destroy_filters and
> qdisc_put_rtab(q->link.R_tab) are already called in cbq_destroy_class.
> The latter lead to a slab corruption due to repeated freeing of
> q->link.R_tab because q->link is part of q->classes. Problem introduced
> in 1.21.
Good catch, applied.
prev parent reply other threads:[~2004-09-16 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 13:28 [PATCH 2.6 NET] Fixes slab corruption in cbq_destroy Thomas Graf
2004-09-16 13:47 ` Patrick McHardy
2004-09-16 14:09 ` Thomas Graf
2004-09-16 14:58 ` Patrick McHardy
2004-09-16 20:33 ` Thomas Graf
2004-09-16 20:29 ` David S. Miller [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=20040916132923.0ac971f8.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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).