From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hannes Frederic Sowa Subject: Re: [BUG] net/ipv4: inconsistent routing table Date: Mon, 10 Aug 2015 13:50:06 +0200 Message-ID: <87y4hjgy6p.fsf@stressinduktion.org> References: <55C1D207.3040905@iogearbox.net> <55C24BAE.7090702@gmail.com> <55C3B8C8.9030507@redhat.com> <55C4D803.3090108@redhat.com> <878u9njaon.fsf@stressinduktion.org> <878u9jijuc.fsf@stressinduktion.org> Mime-Version: 1.0 Content-Type: text/plain Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: Zang MingJie Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Hello, Zang MingJie writes: > Here comes several options: > > 1. reject local next hop w/ EINVAL > 2. delete route when local next hop removed Will also cause some people to complain. > 3. transition between RT_SCOPE_HOST amd RT_SCOPE_LINK I don't understand the scope transition. I know Alex mentioned it for the first time. Maybe he can explain? > 4. document it I prefer that one :) > which one should we choose ? > > 1 will definitely cause compatibility problem Agreed. > 2 is the easiest solution Will definietely cause some people to complain. Bye, Hannes