From: David Miller <davem@davemloft.net>
To: lw@cn.fujitsu.com
Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] ipv6: Fix for adding multicast route for loopback device automatically.
Date: Wed, 07 Dec 2011 15:06:15 -0500 (EST) [thread overview]
Message-ID: <20111207.150615.181825066035193136.davem@davemloft.net> (raw)
In-Reply-To: <4EDF1481.1080106@cn.fujitsu.com>
From: Li Wei <lw@cn.fujitsu.com>
Date: Wed, 07 Dec 2011 15:23:45 +0800
> There is no obvious reason to add a default multicast route for loopback
> devices, otherwise there would be a route entry whose dst.error set to
> -ENETUNREACH that would blocking all multicast packets.
>
> Signed-off-by: Li Wei <lw@cn.fujitsu.com>
I still do not understand the purpose of this change, what problems
does the current behavior cause?
And can you be sure that by making this change, you are not breaking
something, somewhere, that depends upon the current behavior?
next prev parent reply other threads:[~2011-12-07 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 7:23 [PATCH] ipv6: Fix for adding multicast route for loopback device automatically Li Wei
2011-12-07 20:06 ` David Miller [this message]
2011-12-08 0:58 ` Li Wei
2011-12-12 23:49 ` David Miller
2011-12-13 0:56 ` Li Wei
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=20111207.150615.181825066035193136.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lw@cn.fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).