diff options
| author | Dave Chinner <dchinner@redhat.com> | 2024-01-16 09:59:47 +1100 |
|---|---|---|
| committer | Chandan Babu R <chandanbabu@kernel.org> | 2024-02-13 18:07:35 +0530 |
| commit | 2c1e31ed5c88fe5dd9d8b6398cb1ec9cfe0f4d9a (patch) | |
| tree | 89ab89bcce0fb6a2277701c74ea31982362020e5 /fs/xfs/xfs_rmap_item.c | |
| parent | 0b3a76e955ebe3d71a2bcd5990404ed522b40e17 (diff) | |
| download | linux-2c1e31ed5c88fe5dd9d8b6398cb1ec9cfe0f4d9a.tar.gz linux-2c1e31ed5c88fe5dd9d8b6398cb1ec9cfe0f4d9a.tar.bz2 linux-2c1e31ed5c88fe5dd9d8b6398cb1ec9cfe0f4d9a.zip | |
xfs: place intent recovery under NOFS allocation context
When recovery starts processing intents, all of the initial intent
allocations are done outside of transaction contexts. That means
they need to specifically use GFP_NOFS as we do not want memory
reclaim to attempt to run direct reclaim of filesystem objects while
we have lots of objects added into deferred operations.
Rather than use GFP_NOFS for these specific allocations, just place
the entire intent recovery process under NOFS context and we can
then just use GFP_KERNEL for these allocations.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
Diffstat (limited to 'fs/xfs/xfs_rmap_item.c')
| -rw-r--r-- | fs/xfs/xfs_rmap_item.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/xfs/xfs_rmap_item.c b/fs/xfs/xfs_rmap_item.c index a40b92ac81e8..e473124e29cc 100644 --- a/fs/xfs/xfs_rmap_item.c +++ b/fs/xfs/xfs_rmap_item.c @@ -455,7 +455,7 @@ xfs_rui_recover_work( { struct xfs_rmap_intent *ri; - ri = kmem_cache_alloc(xfs_rmap_intent_cache, GFP_NOFS | __GFP_NOFAIL); + ri = kmem_cache_alloc(xfs_rmap_intent_cache, GFP_KERNEL | __GFP_NOFAIL); switch (map->me_flags & XFS_RMAP_EXTENT_TYPE_MASK) { case XFS_RMAP_EXTENT_MAP: |