[PATCH v2] powernv: don't attempt to refetch the FSP dump until the user has explicitly acked it.

This fixes a bug where we would get two events from OPAL with DUMP_AVAIL set (which is valid for OPAL to do) and in the second run of extract_dump() we would fail to free the memory previously allocated for the dump (leaking ~6MB+) as well as on the second dump_read_data() call OPAL would not

Re: [PATCH v2] powernv: don't attempt to refetch the FSP dump until the user has explicitly acked it.

Stewart Smith stew...@linux.vnet.ibm.com wrote: This fixes a bug where we would get two events from OPAL with DUMP_AVAIL set (which is valid for OPAL to do) and in the second run of extract_dump() we would fail to free the memory previously allocated for the dump (leaking ~6MB+) as well as on

Re: [PATCH v2] powernv: don't attempt to refetch the FSP dump until the user has explicitly acked it.

Michael Neuling mi...@neuling.org writes: Stewart Smith stew...@linux.vnet.ibm.com wrote: This fixes a bug where we would get two events from OPAL with DUMP_AVAIL set (which is valid for OPAL to do) and in the second run of extract_dump() we would fail to free the memory previously allocated