From: Patrick McHardy <kaber@trash.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: Maillist netdev <netdev@oss.sgi.com>
Subject: [PATCH PKT_SCHED 0/6]: assorted fixes
Date: Tue, 11 Jan 2005 22:46:14 +0100 [thread overview]
Message-ID: <41E44926.5010701@trash.net> (raw)
Hi Dave,
following are a couple of assorted fixes: a mem leak, locking bugs in two
tc actions, your sch_api.c fix for holding the rtnl while loading modules
ported to act_api.c, and a bug in tcf_exts that prevents using
actions/policers
without a rate estimator.
You can pull all changes from bk://212.42.230.204/net-2.6-sched
Regards
Patrick
Patrick McHardy:
o [PKT_SCHED]: act_api.c: kill some exports
o [PKT_SCHED]: tcf_exts: rate_tlv is optional
o [PKT_SCHED]: act_api.c: drop rtnl for loading modules
o [PKT_SCHED]: tc actions: disable bhs while lock is held in init path
o [PKT_SCHED]: Fix memory leaks in cls_u32.c error path
o [PKT_SCHED]: Use rtattr_parse_nested where appropriate
next reply other threads:[~2005-01-11 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 21:46 Patrick McHardy [this message]
2005-01-14 4:49 ` [PATCH PKT_SCHED 0/6]: assorted fixes David S. 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=41E44926.5010701@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--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).