summaryrefslogtreecommitdiffstats
path: root/Nt32Pkg/Nt32Pkg.fdf
diff options
context:
space:
mode:
authorStar Zeng <star.zeng@intel.com>2013-07-03 09:09:42 +0000
committerlzeng14 <lzeng14@6f19259b-4bc3-4df7-8a09-765794883524>2013-07-03 09:09:42 +0000
commit039a40aa3b4eefbb4a149da4977ab3ef6c483a0f (patch)
treefbb49cb35f0c0d737daf0a84371ba243ed49d1e9 /Nt32Pkg/Nt32Pkg.fdf
parent3e02ebb2bbe0fd4da880511b1f35951e1c4b8404 (diff)
downloadedk2-039a40aa3b4eefbb4a149da4977ab3ef6c483a0f.tar.gz
edk2-039a40aa3b4eefbb4a149da4977ab3ef6c483a0f.tar.bz2
edk2-039a40aa3b4eefbb4a149da4977ab3ef6c483a0f.zip
SecurityPkg: Variable drivers robustly handle crashes during Reclaim().
PEI variable implementation checks only the variable header signature for validity. This does not seem robust if system crash occurred during previous Reclaim() operation. If the crash occurred while FTW was rewriting the variable FV, the signature could be valid even though the rest of the FV isn't valid. Solution: PEI variable and early phase(before FTW protocol ready) of DXE variable can check the FTW last write status provided by FaultTolerantWritePei and determine if all or partial variable data has been backed up in spare block, and then use the backed up data. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Star Zeng <star.zeng@intel.com> Reviewed-by: Liming Gao <liming.gao@intel.com> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@14455 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'Nt32Pkg/Nt32Pkg.fdf')
0 files changed, 0 insertions, 0 deletions