[lustre-devel] [PATCH 08/24] lustre: use truncate_inode_page in place of truncate_complete_page

[NeilBrown]

On Sat, Jun 16 2018, James Simmons wrote:

>> Carrying a local truncate_complete_page() is not good
>> for maintainability.  Linux now used truncate_inode_page,
>> so use that instead.
>> For correct use, we need to pass the mapping to mdc_release_page()
>> rather than trusting page->mapping.
>
> Nak: truncate_inode_page is not exported so it fails to build when lustre
> is configured as a module.

Bother, nor it is.
We could probably use truncate_inode_pages_range() but it isn't a
perfect fit, which seems to suggest that lustre is trying to do
something that no other filesystem finds the need to do.
I'll dig deeper and work out what is really going on.

Thanks,
NeilBrown
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20180616/0991e7c2/attachment.sig>