From: Matthew Wilcox <willy@infradead.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 4/6] xfs: use memalloc_nofs_{save, restore} instead of memalloc_noio*
Date: Mon, 6 Feb 2017 07:39:23 -0800 [thread overview]
Message-ID: <20170206153923.GL2267@bombadil.infradead.org> (raw)
In-Reply-To: <20170206140718.16222-5-mhocko@kernel.org>
On Mon, Feb 06, 2017 at 03:07:16PM +0100, Michal Hocko wrote:
> +++ b/fs/xfs/xfs_buf.c
> @@ -442,17 +442,17 @@ _xfs_buf_map_pages(
> bp->b_addr = NULL;
> } else {
> int retried = 0;
> - unsigned noio_flag;
> + unsigned nofs_flag;
>
> /*
> * vm_map_ram() will allocate auxillary structures (e.g.
> * pagetables) with GFP_KERNEL, yet we are likely to be under
> * GFP_NOFS context here. Hence we need to tell memory reclaim
> - * that we are in such a context via PF_MEMALLOC_NOIO to prevent
> + * that we are in such a context via PF_MEMALLOC_NOFS to prevent
> * memory reclaim re-entering the filesystem here and
> * potentially deadlocking.
> */
This comment feels out of date ... how about:
/*
* vm_map_ram will allocate auxiliary structures (eg page
* tables) with GFP_KERNEL. If that tries to reclaim memory
* by calling back into this filesystem, we may deadlock.
* Prevent that by setting the NOFS flag.
*/
> - noio_flag = memalloc_noio_save();
> + nofs_flag = memalloc_nofs_save();
> do {
> bp->b_addr = vm_map_ram(bp->b_pages, bp->b_page_count,
> -1, PAGE_KERNEL);
Also, I think it shows that this is the wrong place in XFS to be calling
memalloc_nofs_save(). I'm not arguing against including this patch;
it's a step towards where we want to be. I also don't know XFS well
enough to know where to set that flag ;-) Presumably when we start a
transaction ... ?
next prev parent reply other threads:[~2017-02-06 15:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 14:07 [Cluster-devel] [PATCH 0/6 v4] scope GFP_NOFS api Michal Hocko
2017-02-06 14:07 ` [Cluster-devel] [PATCH 1/6] lockdep: allow to disable reclaim lockup detection Michal Hocko
2017-02-06 14:26 ` Matthew Wilcox
2017-02-06 14:34 ` Michal Hocko
2017-02-06 15:24 ` Matthew Wilcox
2017-02-06 15:30 ` Michal Hocko
2017-02-06 14:07 ` [Cluster-devel] [PATCH 2/6] xfs: abstract PF_FSTRANS to PF_MEMALLOC_NOFS Michal Hocko
2017-02-06 14:07 ` [Cluster-devel] [PATCH 3/6] mm: introduce memalloc_nofs_{save, restore} API Michal Hocko
2017-02-06 14:07 ` [Cluster-devel] [PATCH 4/6] xfs: use memalloc_nofs_{save, restore} instead of memalloc_noio* Michal Hocko
2017-02-06 15:39 ` Matthew Wilcox [this message]
2017-02-06 17:44 ` Michal Hocko
2017-02-06 18:32 ` Darrick J. Wong
2017-02-06 18:47 ` Michal Hocko
2017-02-06 19:51 ` Darrick J. Wong
2017-02-06 21:18 ` Michal Hocko
2017-02-06 22:51 ` Dave Chinner
2017-02-07 7:17 ` Michal Hocko
2017-02-06 14:07 ` [Cluster-devel] [PATCH 5/6] jbd2: mark the transaction context with the scope GFP_NOFS context Michal Hocko
2017-02-06 14:07 ` [Cluster-devel] [PATCH 6/6] jbd2: make the whole kjournald2 kthread NOFS safe Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170206153923.GL2267@bombadil.infradead.org \
--to=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).