summaryrefslogtreecommitdiffstats
path: root/BaseTools/Source/Python/AutoGen/ModuleAutoGen.py
diff options
context:
space:
mode:
authorDandan Bi <dandan.bi@intel.com>2019-09-05 15:08:26 +0800
committerHao A Wu <hao.a.wu@intel.com>2019-09-25 10:03:57 +0800
commit2184ededd36b5221699087a8e084e82ee3b3908a (patch)
tree63cd445948233072824cebfd8bf23e04f678a528 /BaseTools/Source/Python/AutoGen/ModuleAutoGen.py
parentf7fdd620e81dd590414184e562b9058f95480b0e (diff)
downloadedk2-2184ededd36b5221699087a8e084e82ee3b3908a.tar.gz
edk2-2184ededd36b5221699087a8e084e82ee3b3908a.tar.bz2
edk2-2184ededd36b5221699087a8e084e82ee3b3908a.zip
MdeModulePkg/PlatformDriOverride: Unload image on EFI_SECURITY_VIOLATION
For the LoadImage() boot service, with EFI_SECURITY_VIOLATION retval, the Image was loaded and an ImageHandle was created with a valid EFI_LOADED_IMAGE_PROTOCOL, but the image can not be started right now. This follows UEFI Spec. But if the caller of LoadImage() doesn't have the option to defer the execution of an image, we can not treat EFI_SECURITY_VIOLATION like any other LoadImage() error, we should unload image for the EFI_SECURITY_VIOLATION to avoid resource leak. This patch is to do error handling for EFI_SECURITY_VIOLATION explicitly for the caller in PlatformDriOverrideDxe which don't have the policy to defer the execution of the image. Cc: Jian J Wang <jian.j.wang@intel.com> Cc: Hao A Wu <hao.a.wu@intel.com> Cc: Liming Gao <liming.gao@intel.com> Cc: Laszlo Ersek <lersek@redhat.com> Cc: Philippe Mathieu-Daude <philmd@redhat.com> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1992 Signed-off-by: Dandan Bi <dandan.bi@intel.com> Reviewed-by: Hao A Wu <hao.a.wu@intel.com> Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>
Diffstat (limited to 'BaseTools/Source/Python/AutoGen/ModuleAutoGen.py')
0 files changed, 0 insertions, 0 deletions