> So, we don't need to introduce a overwriting policy. > I will make a patch using QueryVariableInfo and just writing multiple logs. I don't think that's what Matthew said. Here's the bad scenario he envisions: System is running. It has an OOPs, which gets logged by pstore, and the system carries on running. The new daemon that we said we needed earlier in this e-mail thread finds the entry in pstore and copies it to some place in /var/log and removes the pstore entry - causing pstore to ask EFI (or ERST) backend to erase the record. Firmware does the erase, but doesn't put the space back into the free pool for use. Repeat with more OOPs until all the EFI (or ERST) space has been allocated and then lost into firmware limbo waiting for a reset. Now we panic. Pstore asks EFI "Do you have any space?" EFI replies "No". Pstore can't even overwrite one of the old OOPs records ... because it thinks they have all been erased. So we lose the panic log. -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
