Re: [PATCH 3/3] fs: Use memalloc_nofs_save in generic_perform_write

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Subject: Re: [PATCH 3/3] fs: Use memalloc_nofs_save in generic_perform_write
From: Michal Hocko <mhocko@xxxxxxxxxx>
Date: Thu, 22 Mar 2018 08:10:22 +0100
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, willy@xxxxxxxxxxxxx, david@xxxxxxxxxxxxx, Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
In-reply-to: <20180321224429.15860-4-rgoldwyn@suse.de>
References: <20180321224429.15860-1-rgoldwyn@suse.de> <20180321224429.15860-4-rgoldwyn@suse.de>
User-agent: Mutt/1.9.4 (2018-02-28)

On Wed 21-03-18 17:44:29, Goldwyn Rodrigues wrote:
> From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxx>
> 
> Perform generic_perform_write() under memalloc_nofs because any allocations
> should not recurse into fs writebacks.

Why? What is the deadlock scenario?
-- 
Michal Hocko
SUSE Labs

References:
- [PATCH 0/3] fs: Use memalloc_nofs_save/restore scope API
  - From: Goldwyn Rodrigues
- [PATCH 3/3] fs: Use memalloc_nofs_save in generic_perform_write
  - From: Goldwyn Rodrigues

Prev by Date: Re: [PATCH 2/3] fs: use memalloc_nofs API while shrinking superblock
Next by Date: Re: [patch] mm, thp: do not cause memcg oom for thp
Previous by thread: [PATCH 3/3] fs: Use memalloc_nofs_save in generic_perform_write
Next by thread: [PATCH 28/45] mm: add kernel_[sg]et_mempolicy() helpers; remove in-kernel calls to syscalls
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux