From: Shahar S Matityahu <[email protected]>

Use the same flags we use in the legacy buffer allocation.
Missing __GFP_NOWARN will cause an unwanted warning incase
we fail to allocate.
Missing __GFP_ZERO will give a buffer initially filled with
garbage which can make debug difficult in case our wrap count is zero.

Signed-off-by: Shahar S Matityahu <[email protected]>
Fixes: d47902f9f71d ("iwlwifi: dbg: add apply point logic")
Signed-off-by: Luca Coelho <[email protected]>
---
 drivers/net/wireless/intel/iwlwifi/fw/dbg.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/net/wireless/intel/iwlwifi/fw/dbg.c 
b/drivers/net/wireless/intel/iwlwifi/fw/dbg.c
index 917aafe1a9db..947f282c05a9 100644
--- a/drivers/net/wireless/intel/iwlwifi/fw/dbg.c
+++ b/drivers/net/wireless/intel/iwlwifi/fw/dbg.c
@@ -1697,8 +1697,10 @@ iwl_fw_dbg_buffer_allocation(struct iwl_fw_runtime *fwrt,
            IWL_FW_INI_LOCATION_DRAM_PATH)
                return;
 
-       virtual_addr = dma_alloc_coherent(fwrt->trans->dev, size,
-                                         &phys_addr, GFP_KERNEL);
+       virtual_addr =
+               dma_alloc_coherent(fwrt->trans->dev, size, &phys_addr,
+                                  GFP_KERNEL | __GFP_NOWARN | __GFP_ZERO |
+                                  __GFP_COMP);
 
        /* TODO: alloc fragments if needed */
        if (!virtual_addr)
-- 
2.20.1

Reply via email to