Step through hardware revision list in reverse order

Windows treats the HardwareID list as a decending order of specialization
where the first entry is the most specific, and last entry is least
specific. This can lead to install issues when the newer driver has a
less-specific HardwareID, as the older ("more-specific") HardwareID is
used for the match. Reordering the HardwareID list, so that the newest
revision is first, will stop Windows selecting the wrong driver package
to install.

Signed-off-by: Owen Smith <owen.smith@citrix.com>
Re-factored slightly for code consistency.

Signed-off-by: Paul Durrant <paul.durrant@citrix.com>

diff --git a/src/xenvif/pdo.c b/src/xenvif/pdo.c
index 0294b069af40a1f91bb32836c4036c5b7c563433..428ce0d9182ad2a6006f0558345b328f9869378d 100644 (file)
--- a/src/xenvif/pdo.c
+++ b/src/xenvif/pdo.c
@@ -2045,13 +2045,15 @@ PdoQueryId(
     }
     case BusQueryHardwareIDs:
     case BusQueryCompatibleIDs: {
-        ULONG   Index;
+        LONG    Index;
         ULONG   Length;
 
         Type = REG_MULTI_SZ;
+        Index = ARRAYSIZE(PdoRevision) - 1;
+
         Length = Id.MaximumLength;
 
-        for (Index = 0; Index < ARRAYSIZE(PdoRevision); Index++) {
+        while (Index >= 0) {
             PXENVIF_PDO_REVISION    Revision = &PdoRevision[Index];
 
             status = RtlStringCbPrintfW(Buffer,
@@ -2066,6 +2068,8 @@ PdoQueryId(
 
             Buffer++;
             Length -= sizeof (WCHAR);
+
+            --Index;
         }
 
         status = RtlStringCbPrintfW(Buffer,