From: Andrew Morton <akpm@linux-foundation.org>
To: milan.kocian@wq.cz
Cc: netdev@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 8320] New: replacing route in kernel doesn't send netlink message
Date: Wed, 11 Apr 2007 09:47:40 -0700 [thread overview]
Message-ID: <20070411094740.e7c04b49.akpm@linux-foundation.org> (raw)
In-Reply-To: <200704110937.l3B9b1Kp001053@fire-2.osdl.org>
On Wed, 11 Apr 2007 02:37:01 -0700 bugme-daemon@bugzilla.kernel.org wrote:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=8320
>
> Summary: replacing route in kernel doesn't send netlink message
> Kernel Version: 2.6.20.6
> Status: NEW
> Severity: low
> Owner: shemminger@osdl.org
> Submitter: milan.kocian@wq.cz
>
>
> Most recent kernel where this bug did *NOT* occur: I think all 2.6 kernels
> Distribution: Debian (with vanilla kernel)
> Hardware Environment: PC
> Software Environment: Debian
> Problem Description:
> When you replace route (via ip r r ), no netlink message is sent. Or is it feature?
>
> Steps to reproduce:
> 1. run 'ip monitor all' on one console
> 2. do 'ip r r EXISTING_ROUTE via DST' on second console
> 3. no message on console one
>
> Small patch for fib_hash (tested) but use carefully I am newbie :-) :
>
> --- fib_hash.c.old 2007-04-11 10:39:34.895667672 +0200
> +++ fib_hash.c 2007-04-11 10:41:34.623466280 +0200
> @@ -457,6 +457,8 @@
> fib_release_info(fi_drop);
> if (state & FA_S_ACCESSED)
> rt_cache_flush(-1);
> + rtmsg_fib(RTM_NEWROUTE, key, fa, cfg->fc_dst_len, tb->tb_id,
> + &cfg->fc_nlinfo);
> return 0;
> }
>
> And for fib_trie (not tested):
>
> --- fib_trie.c.old 2007-04-11 10:39:22.728517360 +0200
> +++ fib_trie.c 2007-04-11 10:40:40.778651936 +0200
> @@ -1205,6 +1205,8 @@
> fib_release_info(fi_drop);
> if (state & FA_S_ACCESSED)
> rt_cache_flush(-1);
> + rtmsg_fib(RTM_NEWROUTE, htonl(key), new_fa, plen, tb->tb_id,
> + &cfg->fc_nlinfo);
>
> goto succeeded;
> }
Thanks. We prefer to receive patches via email rather than via bugzilla.
But that's a relatively minor matter - let's see what the net guys think
about the change first ;)
next parent reply other threads:[~2007-04-11 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200704110937.l3B9b1Kp001053@fire-2.osdl.org>
2007-04-11 16:47 ` Andrew Morton [this message]
2007-04-11 18:19 ` [Bugme-new] [Bug 8320] New: replacing route in kernel doesn't send netlink message Patrick McHardy
2007-04-12 17:53 ` Milan Kocián
2007-04-16 4:59 ` Patrick McHardy
2007-04-17 0:10 ` David Miller
2007-04-17 12:58 ` Patrick McHardy
2007-04-18 12:48 ` Milan Kocián
2007-04-18 14:06 ` Patrick McHardy
2007-04-19 11:30 ` Milan Kocián
2007-04-19 12:12 ` Patrick McHardy
2007-04-19 21:42 ` Andrew Morton
2007-04-20 14:07 ` [patch 1/1] networking: fix sending netlink message when replace route Milan Kocian
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=20070411094740.e7c04b49.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=milan.kocian@wq.cz \
--cc=netdev@vger.kernel.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 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).