linux-kernel - [PATCH 2/7] Fscache: Implement uncaching single no-data page

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 Nov 2013 09:25:35 +0800
From:	Li Wang <liwang@...ntukylin.com>
To:	linux-kernel@...r.kernel.org
Cc:	ceph-devel@...r.kernel.org, Sage Weil <sage@...tank.com>,
	linux-fsdevel@...r.kernel.org, Steve French <sfrench@...ba.org>,
	linux-cifs@...r.kernel.org, Milosz Tanski <milosz@...in.com>,
	David Howells <dhowells@...hat.com>, linux-cachefs@...hat.com,
	Li Wang <liwang@...ntukylin.com>
Subject: [PATCH 2/7] Fscache: Implement uncaching single no-data page

Similar to the routine for multiple pages except
that it takes page * as input rather than list head *.

Signed-off-by: Li Wang <liwang@...ntukylin.com>
---
 fs/fscache/page.c |    8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/fs/fscache/page.c b/fs/fscache/page.c
index 7f5c658..0c69f72 100644
--- a/fs/fscache/page.c
+++ b/fs/fscache/page.c
@@ -721,6 +721,14 @@ nobufs:
 }
 EXPORT_SYMBOL(__fscache_alloc_page);
 
+void __fscache_readpage_cancel(struct fscache_cookie *cookie,
+			       struct page *page)
+{
+	if (PageFsCache(page))
+		__fscache_uncache_page(cookie, page);
+}
+EXPORT_SYMBOL(__fscache_readpage_cancel);
+
 /*
  * Unmark pages allocate in the readahead code path (via:
  * fscache_readpages_or_alloc) after delegating to the base filesystem
-- 
1.7.9.5

--
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/