linux.git/fs/ceph/addr.c, branch v3.14.3

ceph: fix dout() compile warnings in ceph_filemap_fault()

2014-01-28T17:57:06+00:00

PAGE_CACHE_SIZE is unsigned long on all architectures, however size_t
is either unsigned int or unsigned long.  Rather than change format
strings, cast PAGE_CACHE_SIZE to size_t to be in line with dout()s in
ceph_page_mkwrite().

Cc: Yan, Zheng 
Signed-off-by: Ilya Dryomov 
Reviewed-by: Sage Weil

ceph fscache: Uncaching no data page from fscache in readpage()

2013-12-31T18:32:03+00:00

Currently, if one new page allocated into fscache in readpage(), however,
with no data read into due to error encountered during reading from OSDs,
the slot in fscache is not uncached. This patch fixes this.

Signed-off-by: Li Wang 
Reviewed-by: Milosz Tanski

ceph: check caps in filemap_fault and page_mkwrite

2013-12-31T18:32:00+00:00

Adds cap check to the page fault handler. The check prevents page
fault handler from adding new page to the page cache while Fcb caps
are being revoked. This solves Fc revoking hang in multiple clients
mmap IO workload.

Signed-off-by: Yan, Zheng 
Reviewed-by: Sage Weil

ceph: Clean up if error occurred in finish_read()

2013-12-13T17:13:28+00:00

Clean up if error occurred rather than going through normal process

Signed-off-by: Li Wang 
Signed-off-by: Yunchuan Wen 
Signed-off-by: Sage Weil

ceph: Avoid data inconsistency due to d-cache aliasing in readpage()

2013-12-13T17:11:38+00:00

If the length of data to be read in readpage() is exactly
PAGE_CACHE_SIZE, the original code does not flush d-cache
for data consistency after finishing reading. This patches fixes
this.

Signed-off-by: Li Wang 
Signed-off-by: Sage Weil

ceph: allocate non-zero page to fscache in readpage()

2013-11-23T19:01:07+00:00

ceph_osdc_readpages() returns number of bytes read, currently,
the code only allocate full-zero page into fscache, this patch
fixes this.

Signed-off-by: Li Wang 
Reviewed-by: Milosz Tanski 
Reviewed-by: Sage Weil

ceph: page still marked private_2

2013-09-06T16:50:12+00:00

Previous patch that allowed us to cleanup most of the issues with pages marked
as private_2 when calling ceph_readpages. However, there seams to be a case in
the error case clean up in start read that still trigers this from time to
time. I've only seen this one a couple times.

BUG: Bad page state in process petabucket  pfn:335b82
page:ffffea000cd6e080 count:0 mapcount:0 mapping:          (null) index:0x0
page flags: 0x200000000001000(private_2)
Call Trace:
 [] dump_stack+0x46/0x58
 [] bad_page+0xc7/0x120
 [] free_pages_prepare+0x10e/0x120
 [] free_hot_cold_page+0x40/0x160
 [] __put_single_page+0x27/0x30
 [] put_page+0x25/0x40
 [] ceph_readpages+0x2e9/0x6f0 [ceph]
 [] __do_page_cache_readahead+0x1af/0x260

Signed-off-by: Milosz Tanski 
Signed-off-by: Sage Weil

ceph: clean PgPrivate2 on returning from readpages

2013-09-06T16:50:11+00:00

In some cases the ceph readapages code code bails without filling all the pages
already marked by fscache. When we return back to readahead code this causes
a BUG.

Signed-off-by: Milosz Tanski

ceph: use fscache as a local presisent cache

2013-09-06T16:50:11+00:00

Adding support for fscache to the Ceph filesystem. This would bring it to on
par with some of the other network filesystems in Linux (like NFS, AFS, etc...)

In order to mount the filesystem with fscache the 'fsc' mount option must be
passed.

Signed-off-by: Milosz Tanski 
Signed-off-by: Sage Weil

ceph: use vfs __set_page_dirty_nobuffers interface instead of doing it inside filesystem

2013-08-27T23:29:44+00:00

Following we will begin to add memcg dirty page accounting around
__set_page_dirty_{buffers,nobuffers} in vfs layer, so we'd better use vfs interface to
avoid exporting those details to filesystems.

Since vfs set_page_dirty() should be called under page lock, here we don't need elaborate
codes to handle racy anymore, and two WARN_ON() are added to detect such exceptions.
Thanks very much for Sage and Yan Zheng's coaching!

I tested it in a two server's ceph environment that one is client and the other is
mds/osd/mon, and run the following fsx test from xfstests:

  ./fsx   1MB -N 50000 -p 10000 -l 1048576
  ./fsx  10MB -N 50000 -p 10000 -l 10485760
  ./fsx 100MB -N 50000 -p 10000 -l 104857600

The fsx does lots of mmap-read/mmap-write/truncate operations and the tests completed
successfully without triggering any of WARN_ON.

Signed-off-by: Sha Zhengju 
Reviewed-by: Sage Weil