From: Souptick Joarder <jrdr.linux@gmail.com>
To: darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org, willy@infradead.org
Subject: [PATCH] fs: xfs: Change return type to vm_fault_t
Date: Sun, 15 Apr 2018 01:35:30 +0530 [thread overview]
Message-ID: <20180414200530.GA20184@jordon-HP-15-Notebook-PC> (raw)
Use new return type vm_fault_t for fault handlers.
Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
---
fs/xfs/xfs_file.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
index 9ea0832..988ec56 100644
--- a/fs/xfs/xfs_file.c
+++ b/fs/xfs/xfs_file.c
@@ -1027,7 +1027,7 @@
* page_lock (MM)
* i_lock (XFS - extent map serialisation)
*/
-static int
+static vm_fault_t
__xfs_filemap_fault(
struct vm_fault *vmf,
enum page_entry_size pe_size,
@@ -1035,7 +1035,7 @@
{
struct inode *inode = file_inode(vmf->vma->vm_file);
struct xfs_inode *ip = XFS_I(inode);
- int ret;
+ vm_fault_t ret;
trace_xfs_filemap_fault(ip, pe_size, write_fault);
@@ -1064,7 +1064,7 @@
return ret;
}
-static int
+static vm_fault_t
xfs_filemap_fault(
struct vm_fault *vmf)
{
@@ -1074,7 +1074,7 @@
(vmf->flags & FAULT_FLAG_WRITE));
}
-static int
+static vm_fault_t
xfs_filemap_huge_fault(
struct vm_fault *vmf,
enum page_entry_size pe_size)
@@ -1087,7 +1087,7 @@
(vmf->flags & FAULT_FLAG_WRITE));
}
-static int
+static vm_fault_t
xfs_filemap_page_mkwrite(
struct vm_fault *vmf)
{
@@ -1099,7 +1099,7 @@
* on write faults. In reality, it needs to serialise against truncate and
* prepare memory for writing so handle is as standard write fault.
*/
-static int
+static vm_fault_t
xfs_filemap_pfn_mkwrite(
struct vm_fault *vmf)
{
--
1.9.1
next reply other threads:[~2018-04-14 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 20:05 Souptick Joarder [this message]
2018-04-14 21:59 ` [PATCH] fs: xfs: Change return type to vm_fault_t Dave Chinner
2018-04-14 22:24 ` Matthew Wilcox
2018-04-15 7:21 ` Christoph Hellwig
2018-04-15 11:11 ` Matthew Wilcox
2018-04-15 12:04 ` Christoph Hellwig
2018-04-15 12:34 ` Matthew Wilcox
2018-04-16 8:57 ` Christoph Hellwig
2018-04-16 11:14 ` Matthew Wilcox
2018-04-16 11:23 ` Christoph Hellwig
2018-04-16 11:31 ` Matthew Wilcox
2018-04-16 17:03 ` Darrick J. Wong
2018-05-30 12:35 ` Souptick Joarder
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=20180414200530.GA20184@jordon-HP-15-Notebook-PC \
--to=jrdr.linux@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=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).