From: Christoph Hellwig <hch@infradead.org>
To: Wei Fang <fangwei1@huawei.com>
Cc: viro@ZenIV.linux.org.uk, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [RFC][PATCH] vfs,mm: fix a dead loop in truncate_inode_pages_range()
Date: Thu, 29 Sep 2016 06:43:57 -0700 [thread overview]
Message-ID: <20160929134357.GA11463@infradead.org> (raw)
In-Reply-To: <1475151010-40166-1-git-send-email-fangwei1@huawei.com>
Can you please add a testcase for this to xfstests?
Thanks!
--
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:[~2016-09-29 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 12:10 [RFC][PATCH] vfs,mm: fix a dead loop in truncate_inode_pages_range() Wei Fang
2016-09-29 13:43 ` Christoph Hellwig [this message]
2016-09-30 0:54 ` Wei Fang
2016-09-30 1:02 ` Dave Chinner
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=20160929134357.GA11463@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=fangwei1@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).