[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080125142603.a73fd7a2.akpm@linux-foundation.org>
Date: Fri, 25 Jan 2008 14:26:03 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: netdev@...r.kernel.org, Joonwoo Park <joonwpark81@...il.com>
Cc: bugme-daemon@...zilla.kernel.org, schwab@...e.de
Subject: Re: [Bugme-new] [Bug 9816] New: cannot replace route
> On Fri, 25 Jan 2008 13:23:49 -0800 (PST) bugme-daemon@...zilla.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@...ux-foundation.org
> ReportedBy: schwab@...e.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)?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists