* btrfs_setsize: Why do we truncate pages beyond newsize?
@ 2015-06-16 12:45 Chandan Rajendra
0 siblings, 0 replies; only message in thread
From: Chandan Rajendra @ 2015-06-16 12:45 UTC (permalink / raw)
To: linux-btrfs
Hello all,
I am trying to fix failures of generic/029 and generic/030 (in
subpagesize-blocksize scenario) using the pagecache_isize_extended() function
provided by the commit "vfs: fix data corruption when blocksize < pagesize for
mmaped data" (90a8020278c1598fafd071736a0846b38510309c).
In btrfs_setsize(), For the "newsize > oldsize" scenario, why do we have
"truncate_pagecache(inode, newsize)" i.e. why do we truncate pages beyond the
new size of the file (where pages normally shouldn't exist at this point of
execution).
--
chandan
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-06-16 12:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-06-16 12:45 btrfs_setsize: Why do we truncate pages beyond newsize? Chandan Rajendra
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox