From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH 1/2 net-next] net_failover: fix net_failover_compute_features() Date: Mon, 04 Jun 2018 09:31:47 -0400 (EDT) Message-ID: <20180604.093147.1707102168081704551.davem@davemloft.net> References: <20180531120124.pc4txiifxnrslbei@kili.mountain> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: sridhar.samudrala@intel.com, netdev@vger.kernel.org, kernel-janitors@vger.kernel.org To: dan.carpenter@oracle.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:46398 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752800AbeFDNbu (ORCPT ); Mon, 4 Jun 2018 09:31:50 -0400 In-Reply-To: <20180531120124.pc4txiifxnrslbei@kili.mountain> Sender: netdev-owner@vger.kernel.org List-ID: From: Dan Carpenter Date: Thu, 31 May 2018 15:01:25 +0300 > @@ -380,7 +380,8 @@ static rx_handler_result_t net_failover_handle_frame(struct sk_buff **pskb) > > static void net_failover_compute_features(struct net_device *dev) > { > - u32 vlan_features = FAILOVER_VLAN_FEATURES & NETIF_F_ALL_FOR_ALL; > + netdev_features_t vlan_features = FAILOVER_VLAN_FEATURES | > + NETIF_F_ALL_FOR_ALL; The type does need to be corrected to netdev_features_t, but the logical operation is correct. It's a policy operation that was simply by-hand propagated all over the place where these kinds of calculations are performed. So vlan_features is starting with a value of 0 intentionally.