[ovmf test] 129121: regressions - FAIL

[osstest service owner <osstest-admin@xenproject.org>]

flight 129121 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129121/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-i386-libvirt            6 libvirt-build            fail REGR. vs. 129113
 build-i386-pvops              6 kernel-build             fail REGR. vs. 129113

Tests which did not succeed, but are not blocking:
 test-amd64-i386-xl-qemuu-ovmf-amd64  1 build-check(1)              blocked n/a

version targeted for testing:
 ovmf                 c09b254bdc6050cc8b580a26558f692f958645d6
baseline version:
 ovmf                 2f6693c283b54666def65e5e0d0b84e48b21cfef

Last test of basis   129113  2018-10-29 00:40:55 Z    0 days
Testing same since   129121  2018-10-29 03:41:45 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Chasel Chiu <chasel.chiu@intel.com>
  Chasel, Chiu <chasel.chiu@intel.com>
  Ruiyu Ni <ruiyu.ni@intel.com>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           fail    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             fail    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          blocked 


------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

Test harness code can be found at
    http://xenbits.xen.org/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
commit c09b254bdc6050cc8b580a26558f692f958645d6
Author: Chasel, Chiu <chasel.chiu@intel.com>
Date:   Fri Oct 26 15:12:33 2018 +0800

    IntelFsp2Pkg: Fixed potentially NULL pointer accessing
    
    REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1280
    
    When copying IDT table in SecMain, the pointer might be
    NULL so added the check to fix it.
    
    Test: Verified on internal platform and boots successfully.
    
    Cc: Jiewen Yao <Jiewen.yao@intel.com>
    Cc: Desimone Nathaniel L <nathaniel.l.desimone@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Chasel Chiu <chasel.chiu@intel.com>

commit 70425456dae16fca23540936c8fb0d2b86776b97
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date:   Thu Oct 25 18:09:46 2018 +0800

    MdeModulePkg/UsbBusPei: Reject descriptor whose length is bad
    
    Today's implementation doesn't check whether the length of
    descriptor is valid before using it.
    
    The patch fixes this issue by syncing the similar fix to UsbBusDxe.
    70c3c2370a2aefe71cf0f6c1a1e063f7d74e1d79
    *MdeModulePkg/UsbBus: Reject descriptor whose length is bad
    
    Additionally the patch also rejects the data when length is
    larger than sizeof (PeiUsbDevice->ConfigurationData).
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
    Reviewed-by: Star Zeng <star.zeng@intel.com>
    Cc: Jiewen Yao <jiewen.yao@intel.com>

commit c96de1dbaedce11489974c3e977f1de4ec5cfb84
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date:   Thu Oct 25 17:07:12 2018 +0800

    MdeModulePkg/UsbBusPei: Fix out-of-bound read access to descriptors
    
    Today's implementation reads the Type/Length field in the USB
    descriptors data without checking whether the offset to read is
    beyond the data boundary.
    
    The patch fixes this issue by syncing the fix in commit
    4c034bf62cbc1f3c5f4b5df25de97f0f528132b2
    *MdeModulePkg/UsbBus: Fix out-of-bound read access to descriptors
    
    ParsedBytes in UsbBusPei.GetExpectedDescriptor() is different from
    Consumed in UsbBusDxe.UsbCreateDesc().
    ParsedBytes is the offset of found descriptor while Consumed is
    offset of next descriptor of found one.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
    Reviewed-by: Star Zeng <star.zeng@intel.com>
    Cc: Jiewen Yao <jiewen.yao@intel.com>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel