All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: jamal <hadi@cyberus.ca>
Cc: Michal Ludvig <mludvig@suse.cz>, Andrew Morton <akpm@osdl.org>,
	Stephen Hemminger <shemminger@osdl.org>,
	netdev@oss.sgi.com, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] rtnetlink & address family problem
Date: Tue, 7 Dec 2004 15:10:33 +0100	[thread overview]
Message-ID: <20041207141033.GD1371@postel.suug.ch> (raw)
In-Reply-To: <1102425618.1089.133.camel@jzny.localdomain>

* jamal <1102425618.1089.133.camel@jzny.localdomain> 2004-12-07 08:20
> On Tue, 2004-12-07 at 08:17, Thomas Graf wrote:
> 
> > It's not really related to the gnet_stats code.  stats_lock isn't set
> > in the action code when using an older iproute2. I haven't tested this
> > case because it was marked as broken anyway. 
> 
> Can you ping my memory on this? Is this tc with initial support
> for actions or something much older than that.

I'm not sure, I'm testing with a version having no action support at
all. It should be fairly easy to find the bug once I have the time to
really look into it. I'm still getting interrupted all the time at
the moment.

All actions created via tcf_hash_create, tcf_police_locate, and
tcf_act_police_locate should be fine. There must be some bogus path
related to older tc versions.

  reply	other threads:[~2004-12-07 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 17:43 [PATCH] rtnetlink & address family problem Michal Ludvig
2004-12-06 11:40 ` jamal
2004-12-06 14:02 ` Thomas Graf
2004-12-07  2:27   ` jamal
2004-12-07 12:49     ` Thomas Graf
2004-12-07 13:02       ` jamal
2004-12-07 13:17         ` Thomas Graf
2004-12-07 13:20           ` jamal
2004-12-07 14:10             ` Thomas Graf [this message]
2004-12-07 16:55               ` Thomas Graf
2004-12-07 17:52         ` Thomas Graf
2004-12-07 19:12           ` Stephen Hemminger

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=20041207141033.GD1371@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=akpm@osdl.org \
    --cc=hadi@cyberus.ca \
    --cc=jack@suse.cz \
    --cc=mludvig@suse.cz \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.