[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [XENVIF PATCH] Fix argument to ControllerSetHashAlgorithm
From what I can tell, xennet will only set NONE or TOEPLITZ. But xenvif defaults the Hash->Algorithm to UNSPECIFIED, so its possible that xennet may not set the algorithm and leave it as default. UNSPECIFIED seems to only be used as a log line to detect when xennet has not set an algorithm. Either UNSPECIFIED should be treated the same as NONE, or removed entirely - though removal would require a change to the interface header, and a version change... switch (Hash->Algorithm) { case XENVIF_PACKET_HASH_ALGORITHM_NONE: case XENVIF_PACKET_HASH_ALGORITHM_UNSPECIFIED: NetifAlgorithm = XEN_NETIF_CTRL_HASH_ALGORITHM_NONE; Size = 1; Mapping = &Zero; Flags = 0; break; adding UNSPECIFIED to this switch in __FrontendUpdateHash is likely the simplest solution. At this point, Size, Mapping and Flags dont need to be assigned when NetifAlgorithm is NONE, as they are not used due to the 'goto done' code path Owen On Wed, Jul 23, 2025 at 9:38 AM Tu Dinh <ngoc-tu.dinh@xxxxxxxxxx> wrote: On 23/07/2025 10:32, Owen Smith wrote:
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |