From: Patrick McHardy <kaber@trash.net>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Krzysztof Oledzki <olel@ans.pl>, netdev@vger.kernel.org
Subject: Re: [PATCH] Fix routing tables with id > 255 for legacy software
Date: Tue, 03 Jun 2008 19:58:42 +0200 [thread overview]
Message-ID: <48458652.7020309@trash.net> (raw)
In-Reply-To: <20080603174941.GA2727@ami.dom.local>
Jarek Poplawski wrote:
> On Tue, Jun 03, 2008 at 05:15:04PM +0200, Krzysztof Oledzki wrote:
>>
>> On Tue, 3 Jun 2008, Patrick McHardy wrote:
> ...
>>> Your patch makes it more predictable, so I'm not completely
>>> opposed, but still its just a workaround.
>> Indeed - it is a workaround but I believe we need it.
>>
>
> IMHO, adding a safety with e.g. CONFIG_IP_FIB_COMPAT_DEPRECATED
> (default N) for one stable, letting to change this back in some
> (probably nonexistent) strange cases, should be enough to keep up
> appearances...
Mhh .. I don't think this is a good solution. Things can
only break if you actually use the new feature, and if
you do, you should simply make sure that all software
running can deal with it. Fixing the routing daemons
should be a triviality.
next prev parent reply other threads:[~2008-06-03 17:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 22:09 [PATCH] Fix routing tables with id > 255 for legacy software Krzysztof Oledzki
2008-06-03 8:08 ` Jarek Poplawski
2008-06-03 10:37 ` Krzysztof Oledzki
2008-06-03 11:33 ` Jarek Poplawski
2008-06-03 11:47 ` Jarek Poplawski
2008-06-03 12:43 ` Patrick McHardy
2008-06-03 13:03 ` Krzysztof Oledzki
2008-06-03 13:10 ` Patrick McHardy
2008-06-03 15:15 ` Krzysztof Oledzki
2008-06-03 17:49 ` Jarek Poplawski
2008-06-03 17:58 ` Patrick McHardy [this message]
2008-06-03 18:29 ` Jarek Poplawski
2008-06-03 18:29 ` Krzysztof Oledzki
2008-06-03 18:42 ` Jarek Poplawski
2008-06-03 18:28 ` Patrick McHardy
2008-06-03 18:39 ` Krzysztof Oledzki
2008-06-03 20:28 ` Patrick McHardy
2008-06-03 23:23 ` Patrick McHardy
2008-06-10 22:45 ` David 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=48458652.7020309@trash.net \
--to=kaber@trash.net \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olel@ans.pl \
/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).