summaryrefslogtreecommitdiffstats
path: root/drivers/usb/host/ohci-ppc-of.c
diff options
context:
space:
mode:
authorStephen Hemminger <shemminger@vyatta.com>2008-08-23 05:16:46 -0700
committerDavid S. Miller <davem@davemloft.net>2008-08-23 05:16:46 -0700
commitf410a1fba7afa79d2992620e874a343fdba28332 (patch)
tree5e08d30678cfadd65a8dfe20bc12160a23faa43d /drivers/usb/host/ohci-ppc-of.c
parentfdc0bde90a689b9145f2b6f271c03f4c99d09667 (diff)
downloadkernel-crypto-f410a1fba7afa79d2992620e874a343fdba28332.tar.gz
kernel-crypto-f410a1fba7afa79d2992620e874a343fdba28332.tar.xz
kernel-crypto-f410a1fba7afa79d2992620e874a343fdba28332.zip
ipv6: protocol for address routes
This fixes a problem spotted with zebra, but not sure if it is necessary a kernel problem. With IPV6 when an address is added to an interface, Zebra creates a duplicate RIB entry, one as a connected route, and other as a kernel route. When an address is added to an interface the RTN_NEWADDR message causes Zebra to create a connected route. In IPV4 when an address is added to an interface a RTN_NEWROUTE message is set to user space with the protocol RTPROT_KERNEL. Zebra ignores these messages, because it already has the connected route. The problem is that route created in IPV6 has route protocol == RTPROT_BOOT. Was this a design decision or a bug? This fixes it. Same patch applies to both net-2.6 and stable. Signed-off-by: Stephen Hemminger <shemminger@vyatta.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/usb/host/ohci-ppc-of.c')
0 files changed, 0 insertions, 0 deletions