From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935184AbcKMUT4 (ORCPT ); Sun, 13 Nov 2016 15:19:56 -0500 Received: from frisell.zx2c4.com ([192.95.5.64]:49942 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935074AbcKMUTy (ORCPT ); Sun, 13 Nov 2016 15:19:54 -0500 MIME-Version: 1.0 In-Reply-To: <405b2e79-854d-4c30-07b0-bd524137d2f6@cumulusnetworks.com> References: <20161113132347.17907-1-Jason@zx2c4.com> <405b2e79-854d-4c30-07b0-bd524137d2f6@cumulusnetworks.com> From: "Jason A. Donenfeld" Date: Sun, 13 Nov 2016 21:19:47 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] ip6_output: ensure flow saddr actually belongs to device To: David Ahern Cc: Netdev , WireGuard mailing list , LKML , YOSHIFUJI Hideaki , Hannes Frederic Sowa Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi David, On Sun, Nov 13, 2016 at 5:30 PM, David Ahern wrote: > You can't require the address to be on the dst device. e.g., it can be an address from the loopback/vrf device. > > This block needs to be done at function entry, and pass dev as NULL to mean is the address assigned to any interface. That gets you the equivalency of the IPv4 check. I gave v2 my best shot. Hopefully it's adequate, but I have a feeling it might be best for you to just code up what you have in mind. Regards, Jason