{"push_id":2806524009,"size":1,"distinct_size":1,"ref":"refs/heads/powerpc_fadump_cleanup_crash_memory_ranges_support_mbox_next","head":"60ebf8e2efd7e7a505937f037258a73a20db7104","before":"f827e0da712f8efe0926ec4dc84083390d509fcf","commits":[{"sha":"60ebf8e2efd7e7a505937f037258a73a20db7104","author":{"name":"Hari Bathini","email":"8c08e0cbfdd898a4d11cb688ad22c29e30def136@linux.ibm.com"},"message":"powerpc/fadump: cleanup crash memory ranges support\n\nCommit 1bd6a1c4b80a (\"powerpc/fadump: handle crash memory ranges array\nindex overflow\") changed crash memory ranges to a dynamic array that\nis reallocated on-demand with krealloc(). The relevant header for this\ncall was not included. The kernel compiles though. But be cautious and\nadd the header anyway.\n\nAlso, memory allocation logic in fadump_add_crash_memory() takes care\nof memory allocation for crash memory ranges in all scenarios. Drop\nunnecessary memory allocation in fadump_setup_crash_memory_ranges().\n\nFixes: 1bd6a1c4b80a (\"powerpc/fadump: handle crash memory ranges array index overflow\")\nCc: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>\nSigned-off-by: Hari Bathini <hbathini@linux.ibm.com>","distinct":true,"url":"https://api.github.com/repos/ruscur/linux/commits/60ebf8e2efd7e7a505937f037258a73a20db7104"}]}
{"actor":{"display_login":"ruscur"}}