aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/libxed.py
diff options
context:
space:
mode:
authorTadeusz Struk <[email protected]>2021-11-11 12:59:16 -0800
committerDavid S. Miller <[email protected]>2021-11-15 12:57:31 +0000
commit86c3a3e964d910a62eeb277d60b2a60ebefa9feb (patch)
tree9cc4ea9af1ca1424789d893353d2efc47b38be58 /tools/perf/scripts/python/libxed.py
parent1aa3b2207e889a948049c9a8016cedb0218c2389 (diff)
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 <[email protected]> Cc: Ying Xue <[email protected]> Cc: "David S. Miller" <[email protected]> Cc: Jakub Kicinski <[email protected]> Cc: [email protected] Cc: [email protected] Cc: [email protected] Signed-off-by: Tadeusz Struk <[email protected]> Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/libxed.py')
0 files changed, 0 insertions, 0 deletions