Double-check safety of rolling memory
Make sure there is no change pending regardless of why maybe_roll_memory has been called. Also, check that the manifest SQN has been incremented before accepting the change. Conflict here would lead to data loss in the penciller, so extra safety is important.
This commit is contained in:
parent
fd2e0e870c
commit
7dd07080c7
2 changed files with 48 additions and 43 deletions
|
@ -98,7 +98,7 @@
|
|||
{"P0008",
|
||||
{info, "Penciller closing for reason ~w"}},
|
||||
{"P0010",
|
||||
{info, "No level zero action on close of Penciller ~w"}},
|
||||
{info, "No level zero action on close of Penciller discarded=~w"}},
|
||||
{"P0011",
|
||||
{info, "Shutdown complete for Penciller for reason ~w"}},
|
||||
{"P0012",
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue