[ovmf baseline-only test] 75550: tolerable FAIL

[ovmf baseline-only test] 75550: tolerable FAIL

[Platform Team regression test user]

This run is configured for baseline tests only.

flight 75550 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75550/

Failures :-/ but no regressions.

Tests which did not succeed, but are not blocking:
 build-amd64-libvirt           6 libvirt-build                fail   like 75548
 test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install      fail like 75548
 build-i386-libvirt            6 libvirt-build                fail   like 75548
 test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install     fail like 75548

version targeted for testing:
 ovmf                 27b9cb33e7437f6aef184c6b2982d004d279cc04
baseline version:
 ovmf                 a0f01e8a22e15000e564f09e82eae13d7127be3c

Last test of basis    75548  2018-10-30 17:57:14 Z    0 days
Testing same since    75550  2018-10-31 05:00:40 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Hao Wu <hao.a.wu@intel.com>

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


------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images

Logs, config files, etc. are available at
    http://osstest.xensource.com/osstest/logs

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


Push not applicable.

------------------------------------------------------------
commit 27b9cb33e7437f6aef184c6b2982d004d279cc04
Author: Hao Wu <hao.a.wu@intel.com>
Date:   Tue Oct 30 09:17:04 2018 +0800

    MdeModulePkg/UdfDxe: Memory free/use after free in ResolveSymlink()
    
    REF:https://bugzilla.tianocore.org/show_bug.cgi?id=1279
    
    For function ResolveSymlink(), the below codes:
    
        if (CompareMem ((VOID *)&PreviousFile, (VOID *)Parent,
                        sizeof (UDF_FILE_INFO)) != 0) {
          CleanupFileInformation (&PreviousFile);
        }
    
        CopyMem ((VOID *)&PreviousFile, (VOID *)File, sizeof (UDF_FILE_INFO));
    
    If the contents in 'PreviousFile' and 'File' are the same, call to
    "CleanupFileInformation (&PreviousFile);" will free the buffers in 'File'
    as well. This will lead to potential memory double free/use after free
    issues.
    
    This commit will add additional check to address the above issue.
    
    Cc: Ruiyu Ni <ruiyu.ni@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Hao Wu <hao.a.wu@intel.com>
    Reviewed-by: Paulo Alcantara <palcantara@suse.de>
    Reviewed-by: Star Zeng <star.zeng@intel.com>
    Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>

commit bfb8c64cbf6a4604b1a69de8e274cce7f0a678dc
Author: Hao Wu <hao.a.wu@intel.com>
Date:   Tue Oct 30 09:11:57 2018 +0800

    MdeModulePkg/UdfDxe: Content check for 'File' in ResolveSymlink()
    
    REF:https://bugzilla.tianocore.org/show_bug.cgi?id=1279
    
    The content within 'File' is the output data for ResolveSymlink(). This
    commit will add checks to ensure the content in 'File' is valid.
    Otherwise, possible null pointer dereference issue will occur during the
    subsequent usage of the data returned by ResolveSymlink().
    
    Cc: Ruiyu Ni <ruiyu.ni@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Hao Wu <hao.a.wu@intel.com>
    Reviewed-by: Paulo Alcantara <palcantara@suse.de>
    Reviewed-by: Star Zeng <star.zeng@intel.com>
    Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>

commit 542b03d0a090d10d39da79a881787cbb013f1754
Author: Hao Wu <hao.a.wu@intel.com>
Date:   Tue Oct 30 09:06:48 2018 +0800

    MdeModulePkg/UdfDxe: Check 'Component Type' within a Path Component
    
    REF:https://bugzilla.tianocore.org/show_bug.cgi?id=1279
    
    According to the ECMA-167 standard (3rd Edition - June 1997), Section
    14.16.1.1, valid values are 1 to 5. All other values will be treated as a
    corrupted volume.
    
    This commit will add such check within function ResolveSymlink().
    
    Cc: Ruiyu Ni <ruiyu.ni@intel.com>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Hao Wu <hao.a.wu@intel.com>
    Reviewed-by: Paulo Alcantara <palcantara@suse.de>
    Reviewed-by: Star Zeng <star.zeng@intel.com>
    Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>

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