linux-kernel - [RFC 1/1] fs/omfs/file.c: use mpage_readpage() instead of block_read_full

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1432329777-14045-1-git-send-email-fabf@skynet.be>
Date:	Fri, 22 May 2015 23:22:56 +0200
From:	Fabian Frederick <fabf@...net.be>
To:	linux-kernel@...r.kernel.org
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Fabian Frederick <fabf@...net.be>,
	Bob Copeland <me@...copeland.com>,
	linux-karma-devel@...ts.sourceforge.net
Subject: [RFC 1/1] fs/omfs/file.c: use mpage_readpage() instead of block_read_full_page()

OMFS uses mpage_readpages() for .readpages which proves it's based on pagecache.
Use mpage_readpage() instead of slower bh based block_read_full_page()
for .readpage.

Is there some test I could link to the patch changelog ?
(.readpage seems mainly used in mm/filemap)

Regards,
Fabian

Signed-off-by: Fabian Frederick <fabf@...net.be>
---
 fs/omfs/file.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/omfs/file.c b/fs/omfs/file.c
index d9e26cf..672d3c2 100644
--- a/fs/omfs/file.c
+++ b/fs/omfs/file.c
@@ -286,7 +286,7 @@ out:
 
 static int omfs_readpage(struct file *file, struct page *page)
 {
-	return block_read_full_page(page, omfs_get_block);
+	return mpage_readpage(page, omfs_get_block);
 }
 
 static int omfs_readpages(struct file *file, struct address_space *mapping,
-- 
2.4.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/