[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180604.093147.1707102168081704551.davem@davemloft.net>
Date: Mon, 04 Jun 2018 09:31:47 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: dan.carpenter@...cle.com
Cc: sridhar.samudrala@...el.com, netdev@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 1/2 net-next] net_failover: fix
net_failover_compute_features()
From: Dan Carpenter <dan.carpenter@...cle.com>
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.
Powered by blists - more mailing lists