| commit | ed415480c9c6a8e103c77fd6d1ab8510d6a70709 | |
| author | tian, feng <eric_tian@tianocore.org> | |
| Mon, 16 Mar 2009 09:57:10 +0000 (16 09:57 +0000) | ||
| committer | tian, feng <eric_tian@tianocore.org> | |
| Mon, 16 Mar 2009 09:57:10 +0000 (16 09:57 +0000) | ||
| tree | 523619e3dde3aabb7a16c4f96cf9b6bf58963bf5 | treesnapshot (tar.gz zip) |
| parent | eb5099b4de1d086dd19f832769594a3271aa4f03 | commitdiff |
Fix tracker 202216:linux runtime test issue.
[Root Cause]
The root cause is that in FindVariable function, original code logic will traverse all variable stored in variable volatile/non-volatile area. If the non-variable area is full and Linux sets a new variable, the caller of GetNextVariablePtr will get the address of next memory block, but this block doesn't be reserved as RUNTIME attribute. Therefore its corresponding page translation table doesn't exist and causes linux kernel panic.
[Root Cause]
The root cause is that in FindVariable function, original code logic will traverse all variable stored in variable volatile/non-volatile area. If the non-variable area is full and Linux sets a new variable, the caller of GetNextVariablePtr will get the address of next memory block, but this block doesn't be reserved as RUNTIME attribute. Therefore its corresponding page translation table doesn't exist and causes linux kernel panic.
| MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c | diffblobblamehistory |