1.. _skiboot-5.10.6: 2 3============== 4skiboot-5.10.6 5============== 6 7skiboot 5.10.6 was released on Monday May 28th, 2018. It replaces 8:ref:`skiboot-5.10.5` as the current stable release in the 5.10.x series. 9 10It is recommended that 5.10.6 be used instead of any previous 5.10.x version, 11especially due to the locking bug fixes. 12 13It is expected that this will be the final 5.10.x version, with 6.0.x taking 14over as the main stable branch. 15 16Over :ref:`skiboot-5.10.5`, we have the following fixes: 17 18- opal-prd: Do not error out on first failure for soft/hard offline. 19 20 The memory errors (CEs and UEs) that are detected as part of background 21 memory scrubbing are reported by PRD asynchronously to opal-prd along with 22 affected memory ranges. hservice_memory_error() converts these ranges into 23 page granularity before hooking up them to soft/hard offline-ing 24 infrastructure. 25 26 But the current implementation of hservice_memory_error() does not hookup 27 all the pages to soft/hard offline-ing if any of the page offline action 28 fails. e.g hard offline can fail for: 29 30 - Pages that are not part of buddy managed pool. 31 - Pages that are reserved by kernel using memblock_reserved() 32 - Pages that are in use by kernel. 33 34 But for the pages that are in use by user space application, the hard 35 offline marks the page as hwpoison, sends SIGBUS signal to kill the 36 affected application as recovery action and returns success. 37 38 Hence, It is possible that some of the pages in that memory range are in 39 use by application or free. By stopping on first error we loose the 40 opportunity to hwpoison the subsequent pages which may be free or in use by 41 application. This patch fixes this issue. 42- xive: fix missing unlock in error path 43 44 Found with sparse and some added lock annotations. 45- OPAL_PCI_SET_POWER_STATE: fix locking in error paths 46 47 Otherwise we could exit OPAL holding locks, potentially leading 48 to all sorts of problems later on. 49