linux-kernel - Re: [PATCH] tipc: use consistent GFP flags

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 15 Nov 2021 13:00:08 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Tadeusz Struk <tadeusz.struk@...aro.org>
Cc:     jmaloy@...hat.com, ying.xue@...driver.com, davem@...emloft.net,
        kuba@...nel.org, netdev@...r.kernel.org,
        tipc-discussion@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tipc: use consistent GFP flags

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@...emloft.net>:

On Thu, 11 Nov 2021 12:59:16 -0800 you wrote:
> Some functions, like tipc_crypto_start use inconsisten GFP flags
> when allocating memory. The mentioned function use GFP_ATOMIC to
> to alloc a crypto instance, and then calls alloc_ordered_workqueue()
> which allocates memory with GFP_KERNEL. tipc_aead_init() function
> even uses GFP_KERNEL and GFP_ATOMIC interchangeably.
> No doc comment specifies what context a function is designed to
> work in, but the flags should at least be consistent within a function.
> 
> [...]

Here is the summary with links:
  - tipc: use consistent GFP flags
    https://git.kernel.org/netdev/net/c/86c3a3e964d9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html