summaryrefslogtreecommitdiff
path: root/net/rxrpc
diff options
context:
space:
mode:
authorTadeusz Struk <tadeusz.struk@linaro.org>2021-11-11 23:59:16 +0300
committerDavid S. Miller <davem@davemloft.net>2021-11-15 15:57:31 +0300
commit86c3a3e964d910a62eeb277d60b2a60ebefa9feb (patch)
tree9cc4ea9af1ca1424789d893353d2efc47b38be58 /net/rxrpc
parent1aa3b2207e889a948049c9a8016cedb0218c2389 (diff)
downloadlinux-86c3a3e964d910a62eeb277d60b2a60ebefa9feb.tar.xz
tipc: use consistent GFP flags
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. Cc: Jon Maloy <jmaloy@redhat.com> Cc: Ying Xue <ying.xue@windriver.com> Cc: "David S. Miller" <davem@davemloft.net> Cc: Jakub Kicinski <kuba@kernel.org> Cc: netdev@vger.kernel.org Cc: tipc-discussion@lists.sourceforge.net Cc: linux-kernel@vger.kernel.org Signed-off-by: Tadeusz Struk <tadeusz.struk@linaro.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/rxrpc')
0 files changed, 0 insertions, 0 deletions