GitHub PushEvent at 2014-03-23 20:55:36
Repository: kernel_lge_geeb
Actor: slimgerrit
Payload: {"shas":[["e612daf7187b65972a7c0a869d01fb208c89b942","bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com","iwlwifi: protect SRAM debugfs\n\ncommit 4fc79db178f0a0ede479b4713e00df2d106028b3 upstream.\n\nIf the device is not started, we can't read its\nSRAM and attempting to do so will cause issues.\nProtect the debugfs read.\n\nChange-Id: I29341da57bbef08f7b5c1126fe5a56a296aee1d4\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nSigned-off-by: John W. Linville <linville@tuxdriver.com>\n[wujg: Backported to 3.4: adjust context]\nSigned-off-by: Jianguo Wu <wujianguo@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Johannes Berg",true],["291a59355a0ba910e17a35f11a90e140202e730c","643a80aaf16a8332d6a70921c14d4bb265446494@intel.com","iwlwifi: don't handle masked interrupt\n\ncommit 25a172655f837bdb032e451f95441bb4acec51bb upstream.\n\nThis can lead to a panic if the driver isn't ready to\nhandle them. Since our interrupt line is shared, we can get\nan interrupt at any time (and CONFIG_DEBUG_SHIRQ checks\nthat even when the interrupt is being freed).\n\nIf the op_mode has gone away, we musn't call it. To avoid\nthis the transport disables the interrupts when the hw is\nstopped and the op_mode is leaving.\nIf there is an event that would cause an interrupt the INTA\nregister is updated regardless of the enablement of the\ninterrupts: even if the interrupts are disabled, the INTA\nwill be changed, but the device won't issue an interrupt.\nBut the ISR can be called at any time, so we ought ignore\nthe value in the INTA otherwise we can call the op_mode\nafter it was freed.\n\nI found this bug when the op_mode_start failed, and called\niwl_trans_stop_hw(trans, true). Then I played with the\nRFKILL button, and removed the module.\nWhile removing the module, the IRQ is freed, and the ISR is\ncalled (CONFIG_DEBUG_SHIRQ enabled). Panic.\n\nChange-Id: Ia36f5dade9e0e3bc6adaea0c83dfb7eb43b3b57f\nSigned-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nReviewed-by: Gregory Greenman <gregory.greenman@intel.com>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\n[bwh: Backported to 3.2:\n - Adjust context\n - Pass bus(trans), not trans, to iwl_{read,write}32()]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\n[wujg: Backported to 3.4:\n - adjust context\n - Pass trans to iwl_{read,write}32()}]\nSigned-off-by: Jianguo Wu <wujianguo@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Emmanuel Grumbach",true],["240695be5e0799349c723893b7177fcda3feb81a","bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com","iwlwifi: handle DMA mapping failures\n\ncommit 7c34158231b2eda8dcbd297be2bb1559e69cb433 upstream.\n\nThe RX replenish code doesn't handle DMA mapping failures,\nwhich will cause issues if there actually is a failure. This\nwas reported by Shuah Khan who found a DMA mapping framework\nwarning (\"device driver failed to check map error\").\n\nChange-Id: Icc8261e442e7a56f289f85331617bca0ea8130af\nReported-by: Shuah Khan <shuah.khan@hp.com>\nReviewed-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\n[bwh: Backported to 3.2:\n - Adjust filename, context, indentation\n - Use bus(trans) instead of trans where necessary\n - Use hw_params(trans).rx_page_order instead of trans_pcie->rx_page_order]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\n[wujg: Backported to 3.4:\n - Adjust context\n - Use trans instead of bus(trans)\n - Use hw_params(trans).rx_page_order instead of trans_pcie->rx_page_order]\nSigned-off-by: Jianguo Wu <wujianguo@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Johannes Berg",true],["565b3ed11185ca9dcaf6240d7b749d206af43f9f","bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com","iwlwifi: always copy first 16 bytes of commands\n\ncommit 8a964f44e01ad3bbc208c3e80d931ba91b9ea786 upstream.\n\nThe FH hardware will always write back to the scratch field\nin commands, even host commands not just TX commands, which\ncan overwrite parts of the command. This is problematic if\nthe command is re-used (with IWL_HCMD_DFL_NOCOPY) and can\ncause calibration issues.\n\nAddress this problem by always putting at least the first\n16 bytes into the buffer we also use for the command header\nand therefore make the DMA engine write back into this.\n\nFor commands that are smaller than 16 bytes also always map\nenough memory for the DMA engine to write back to.\n\nChange-Id: I4992d0115fa24d23abe9c3225bad28bfe0483570\nReviewed-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\n[bwh: Backported to 3.2:\n - Adjust context\n - Drop the IWL_HCMD_DFL_DUP handling\n - Fix descriptor addresses and lengths for tracepoint, but otherwise\n   leave it unchanged]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\n[wujg: Backported to 3.4: adjust context]\nSigned-off-by: Jianguo Wu <wujianguo@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Johannes Berg",true]],"size":4,"ref":"refs/heads/kk4.4","head":"565b3ed11185ca9dcaf6240d7b749d206af43f9f"}