summaryrefslogtreecommitdiff
path: root/NetworkPkg/IpSecDxe
diff options
context:
space:
mode:
authorStar Zeng <star.zeng@intel.com>2013-07-03 09:08:40 +0000
committerlzeng14 <lzeng14@6f19259b-4bc3-4df7-8a09-765794883524>2013-07-03 09:08:40 +0000
commit3e02ebb2bbe0fd4da880511b1f35951e1c4b8404 (patch)
tree95fc155e9d76e163cd295db373734cc276f4abc6 /NetworkPkg/IpSecDxe
parent70066a82a54bd5136556dff3ea76dff035a3aca3 (diff)
downloadedk2-platforms-3e02ebb2bbe0fd4da880511b1f35951e1c4b8404.tar.xz
MdeModulePkg: 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: Add a FaultTolerantWritePei driver to check and provide the FTW last write status, then PEI variable and early phase(before FTW protocol ready) of DXE variable can check the status 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@14454 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'NetworkPkg/IpSecDxe')
0 files changed, 0 insertions, 0 deletions