From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org, Joonwoo Park <joonwpark81@gmail.com>
Cc: bugme-daemon@bugzilla.kernel.org, schwab@suse.de
Subject: Re: [Bugme-new] [Bug 9816] New: cannot replace route
Date: Fri, 25 Jan 2008 14:26:03 -0800 [thread overview]
Message-ID: <20080125142603.a73fd7a2.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9816-10286@http.bugzilla.kernel.org/>
> On Fri, 25 Jan 2008 13:23:49 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9816
>
> Summary: cannot replace route
> Product: Networking
> Version: 2.5
> KernelVersion: 2.6.24
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: IPV4
> AssignedTo: shemminger@linux-foundation.org
> ReportedBy: schwab@suse.de
>
>
> Latest working kernel version: 2.6.24-rc8
> Earliest failing kernel version: 2.6.24
> Distribution: SuSE 10.3
> Hardware Environment: ppc32/ppc64
> Software Environment:
> Problem Description:
> ip route replace always fails with EEXIST. (del+add still works.)
>
> Steps to reproduce:
> # ip ro show 127.0.0.0/8
> 127.0.0.0/8 dev lo scope link
> # ip ro rep 127.0.0.0/8 dev lo
> RTNETLINK answers: File exists
>
> Broken by bd566e7525b5986864e8d6eb5b67640abcd284a9.
>
There is a bit more discussion in the bugzilla writeup.
I'd agree with Andrea: replacing a route with itself a) used to work and b)
should still work (surely)?
next parent reply other threads:[~2008-01-25 22:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9816-10286@http.bugzilla.kernel.org/>
2008-01-25 22:26 ` Andrew Morton [this message]
2008-01-25 23:11 ` [Bugme-new] [Bug 9816] New: cannot replace route Jarek Poplawski
2008-01-26 3:20 ` Andrew Morton
2008-01-26 5:16 ` Joonwoo Park
2008-01-26 11:40 ` Jarek Poplawski
2008-01-26 14:10 ` Jarek Poplawski
2008-01-26 14:27 ` Andreas Schwab
2008-01-26 15:19 ` Jarek Poplawski
2008-01-27 1:11 ` Jarek Poplawski
2008-01-27 7:58 ` Jarek Poplawski
2008-01-27 9:49 ` Julian Anastasov
2008-01-27 11:14 ` Jarek Poplawski
2008-01-26 14:32 ` Jarek Poplawski
2008-01-26 12:10 ` Jarek Poplawski
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=20080125142603.a73fd7a2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=joonwpark81@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=schwab@suse.de \
/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.