From: Hugo Santos <hugo@innerghost.net>
To: netdev@oss.sgi.com
Cc: davem@redhat.com
Subject: sch_dsmark bug
Date: Sun, 11 Apr 2004 13:43:06 +0100 [thread overview]
Message-ID: <40793D5A.9060706@innerghost.net> (raw)
Hi there,
I tried to contact the person whose name is in the source file but with
no success. While developing some code that handles with kernel's TC
objects direcly (by netlink) i found a small problem with dsmark (maybe
other scheds have it too, but i haven't checked). This is in linux 2.6.4
(there is no change in this context in 2.6.5); in dsmark_init, if opt is
NULL, the module will crash and TC will get stuck. the module will have a
ref count of 1 so i can't unload it, and i can't change any other TC
stuff since the netlink socket gets stuck when dsmark crashes. So, a simple
if (!opt) return -EINVAL;
would prevent such problems.
If you prefer i may send a patch, but since it's only a one line patch i didn't
send one.
Best regards,
Hugo Santos
next reply other threads:[~2004-04-11 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-11 12:43 Hugo Santos [this message]
2004-04-11 19:43 ` sch_dsmark bug jamal
2004-04-11 22:52 ` Sven Schuster
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=40793D5A.9060706@innerghost.net \
--to=hugo@innerghost.net \
--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).