aboutsummaryrefslogtreecommitdiff
path: root/tools/testing/selftests/bpf/prog_tests/autoload.c
diff options
context:
space:
mode:
authorAlexander Mikhalitsyn <[email protected]>2023-12-08 16:10:22 +0100
committerChristian Brauner <[email protected]>2023-12-12 14:24:54 +0100
commit2b46a19db0a1769a25adc65d1784b68bd8b60046 (patch)
treeb8a7fdd910d0dda5bc1b2ada60835b38f3c62fe3 /tools/testing/selftests/bpf/prog_tests/autoload.c
parent02105f18a26c985a47b40b7401541535ab78a1dd (diff)
fs: super: use GFP_KERNEL instead of GFP_USER for super block allocation
There is no reason to use a GFP_USER flag for struct super_block allocation in the alloc_super(). Instead, let's use GFP_KERNEL for that. >From the memory management perspective, the only difference between GFP_USER and GFP_KERNEL is that GFP_USER allocations are tied to a cpuset, while GFP_KERNEL ones are not. There is no real issue and this is not a candidate to go to the stable, but let's fix it for a consistency sake. Cc: Jan Kara <[email protected]> Cc: Alexander Viro <[email protected]> Cc: Christian Brauner <[email protected]> Cc: <[email protected]> Cc: <[email protected]> Signed-off-by: Alexander Mikhalitsyn <[email protected]> Link: https://lore.kernel.org/r/[email protected] Reviewed-by: Jan Kara <[email protected]> Signed-off-by: Christian Brauner <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions