Don't close file twice in should_use_fallback error path
When fallback.efi is not present, the should_use_fallback error path
attempts to close a file that has already been closed, resulting in a
hang. This issue only affects certain systems.
This is a regression from version 0.8 and was introduced by commit
4794822.
Signed-off-by: Benjamin Antin <email address hidden>
You guys just need to rebase Yakkety's shim package on top of an upstream git commit that comes after 7052e7530755. (Alternatively, you can also backport 7052e7530755, but I guess Yakkety's release schedule might allow another rebase at this point.) You are currently based on 14a5905, which does not include the fix.
Actually, I don't need to write any new patches, upstream shim has the problem fixed already:
commit 7052e75307553ed c8f04eb529b0d37 844fbcc30b
Author: Benjamin Antin <email address hidden>
Date: Mon Jul 18 12:28:12 2016 -0700
Don't close file twice in should_use_fallback error path
When fallback.efi is not present, the should_use_fallback error path
attempts to close a file that has already been closed, resulting in a
hang. This issue only affects certain systems.
This is a regression from version 0.8 and was introduced by commit
4794822.
You guys just need to rebase Yakkety's shim package on top of an upstream git commit that comes after 7052e7530755. (Alternatively, you can also backport 7052e7530755, but I guess Yakkety's release schedule might allow another rebase at this point.) You are currently based on 14a5905, which does not include the fix.