diff options
author | Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com> | 2023-12-08 18:10:22 +0300 |
---|---|---|
committer | Christian Brauner <brauner@kernel.org> | 2023-12-12 16:24:54 +0300 |
commit | 2b46a19db0a1769a25adc65d1784b68bd8b60046 (patch) | |
tree | b8a7fdd910d0dda5bc1b2ada60835b38f3c62fe3 /lib/pci_iomap.c | |
parent | 02105f18a26c985a47b40b7401541535ab78a1dd (diff) | |
download | linux-2b46a19db0a1769a25adc65d1784b68bd8b60046.tar.xz |
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 <jack@suse.cz>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Christian Brauner <brauner@kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Signed-off-by: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Link: https://lore.kernel.org/r/20231208151022.156273-1-aleksandr.mikhalitsyn@canonical.com
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'lib/pci_iomap.c')
0 files changed, 0 insertions, 0 deletions