Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 19 Mar 2018 20:04:34 +0200
From:   Ido Schimmel <idosch@mellanox.com>
To:     Sasha Levin <Alexander.Levin@microsoft.com>
Cc:     "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "stable@vger.kernel.org" <stable@vger.kernel.org>,
        "David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH AUTOSEL for 4.15 058/124] ipv6: Set nexthop flags during
 route creation
Message-ID: <20180319180434.GA13336@splinter>
References: <20180319154645.11350-1-alexander.levin@microsoft.com>
 <20180319154645.11350-58-alexander.levin@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180319154645.11350-58-alexander.levin@microsoft.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Received-SPF: None (protection.outlook.com: mellanox.com does not designate
 permitted sender hosts)
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 Mar 2018 18:04:38.2514 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 040012a2-cf28-424e-bf9d-08d58dc3e187
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: a652971c-7d2e-4d9b-a6a4-d149256f461b
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0501MB2016
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Mar 19, 2018 at 03:48:00PM +0000, Sasha Levin wrote:
> From: Ido Schimmel <idosch@mellanox.com>
> 
> [ Upstream commit 5609b80a37f69f796548339e675256188b29c17d ]
> 
> It is valid to install routes with a nexthop device that does not have a
> carrier, so we need to make sure they're marked accordingly.
> 
> As explained in the previous patch, host and anycast routes are never
> marked with the 'linkdown' flag.
> 
> Note that reject routes are unaffected, as these use the loopback device
> which always has a carrier.
> 
> Signed-off-by: Ido Schimmel <idosch@mellanox.com>
> Acked-by: David Ahern <dsahern@gmail.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> Signed-off-by: Sasha Levin <alexander.levin@microsoft.com>

Hi Sasha,

It doesn't really make sense to take this patch to 4.15 (and 4.14 from
your other mail). The flag is never used there.

In these kernels the flag is dumped to user space based on a carrier
check. See commit 44c9f2f206f8 ("ipv6: Check nexthop flags in route dump
instead of carrier").

Similarly, during route lookup the carrier is checked and not the flag.
See commit 14c5206c2d02 ("ipv6: Check nexthop flags during route lookup
instead of carrier").

Thanks