From: Andrew Morton <akpm@linux-foundation.org>
To: mhocko@kernel.org
Cc: linux-mm@kvack.org, Dave Chinner <david@fromorbit.com>,
Theodore Ts'o <tytso@mit.edu>, Ming Lei <ming.lei@canonical.com>,
Andreas Dilger <andreas.dilger@intel.com>,
Oleg Drokin <oleg.drokin@intel.com>,
Al Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
linux-nfs@vger.kernel.org, linux-cifs@vger.kernel.org,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] mm, fs: Obey gfp_mapping for add_to_page_cache
Date: Tue, 29 Sep 2015 15:02:46 -0700 [thread overview]
Message-ID: <20150929150246.286cc6013bce3eec170376aa@linux-foundation.org> (raw)
In-Reply-To: <1443193461-31402-1-git-send-email-mhocko@kernel.org>
On Fri, 25 Sep 2015 17:04:21 +0200 mhocko@kernel.org wrote:
> From: Michal Hocko <mhocko@suse.com>
>
> 6afdb859b710 ("mm: do not ignore mapping_gfp_mask in page cache
> allocation paths) has caught some users of hardcoded GFP_KERNEL
> used in the page cache allocation paths. This, however, wasn't complete
> and there were others which went unnoticed.
>
> Dave Chinner has reported the following deadlock for xfs on loop device:
> : With the recent merge of the loop device changes, I'm now seeing
> : XFS deadlock on my single CPU, 1GB RAM VM running xfs/073.
> :
> : The deadlocked is as follows:
> :
> : kloopd1: loop_queue_read_work
> : xfs_file_iter_read
> : lock XFS inode XFS_IOLOCK_SHARED (on image file)
> : page cache read (GFP_KERNEL)
> : radix tree alloc
> : memory reclaim
> : reclaim XFS inodes
> : log force to unpin inodes
> : <wait for log IO completion>
> :
> : xfs-cil/loop1: <does log force IO work>
> : xlog_cil_push
> : xlog_write
> : <loop issuing log writes>
> : xlog_state_get_iclog_space()
> : <blocks due to all log buffers under write io>
> : <waits for IO completion>
> :
> : kloopd1: loop_queue_write_work
> : xfs_file_write_iter
> : lock XFS inode XFS_IOLOCK_EXCL (on image file)
> : <wait for inode to be unlocked>
> :
> : i.e. the kloopd, with it's split read and write work queues, has
> : introduced a dependency through memory reclaim. i.e. that writes
> : need to be able to progress for reads make progress.
> :
> : The problem, fundamentally, is that mpage_readpages() does a
> : GFP_KERNEL allocation, rather than paying attention to the inode's
> : mapping gfp mask, which is set to GFP_NOFS.
> :
> : The didn't used to happen, because the loop device used to issue
> : reads through the splice path and that does:
> :
> : error = add_to_page_cache_lru(page, mapping, index,
> : GFP_KERNEL & mapping_gfp_mask(mapping));
>
> This has changed by aa4d86163e4 (block: loop: switch to VFS ITER_BVEC).
xfs-on-loop deadlocks since April would appear to warrant a -stable
backport, yes?
> this is a rebase on top of the current mmotm
> (2015-09-22-15-28)
So I've redone the patch against current mainline.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-09-29 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 15:04 [PATCH] mm, fs: Obey gfp_mapping for add_to_page_cache mhocko
2015-09-29 22:02 ` Andrew Morton [this message]
2015-10-01 11:30 ` 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=20150929150246.286cc6013bce3eec170376aa@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andreas.dilger@intel.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=ming.lei@canonical.com \
--cc=oleg.drokin@intel.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=xfs@oss.sgi.com \
/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).