Date: Fri, 11 May 2018 03:21:46 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Rodney W. Grimes" <freebsd@pdx.rh.CN85.dnsmgr.net> Cc: rgrimes@freebsd.org, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r333476 - head/sys/net Message-ID: <86po23vvf9.fsf@next.des.no> In-Reply-To: <201805110101.w4B11m6w072994@pdx.rh.CN85.dnsmgr.net> (Rodney W. Grimes's message of "Thu, 10 May 2018 18:01:48 -0700 (PDT)") References: <201805110101.w4B11m6w072994@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Rodney W. Grimes" <freebsd@pdx.rh.CN85.dnsmgr.net> writes: > "Dag-Erling Sm=C3=B8rgrav" <des@FreeBSD.org> writes: > > In ifa_maintain_loopback_route(), don't needlessly log an error if we > > either failed to add a route because it already existed or failed to > > remove one because it did not. We still return an error code, though. > Those are the only conditions under which I have ever seen this code > log anything. These usually occur for me when a tunX device is going > down, the route gets ripped out long before maintain_loopback ever has > a chance to remove it. I have a few routers with hundreds of dynamically configured vlan interfaces, so I get a *lot* of these... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86po23vvf9.fsf>