.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "BLOCK_INVALIDATEPAGE" "" "06 October 2005" "" ""

.SH NAME
block_invalidatepage \- invalidate part of all of a buffer-backed page
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int block_invalidatepage  (struct page * \fIpage\fB, unsigned long \fIoffset\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIpage\fB\fR
the page which is affected
.TP
\fB\fIoffset\fB\fR
the index of the truncation point
.SH "DESCRIPTION"
.PP
\fBblock_invalidatepage\fR is called when all or part of the page has become
invalidatedby a truncate operation.
.PP
\fBblock_invalidatepage\fR does not have to release all buffers, but it must
ensure that no dirty buffer is left outside \fIoffset\fR and that no I/O
is underway against any of the blocks which are outside the truncation
point.  Because the caller is about to free (and possibly reuse) those
blocks on-disk.
.SH "DESCRIPTION"
.PP
\fBblock_invalidatepage\fR is called when all or part of the page has become
invalidatedby a truncate operation.
.PP
\fBblock_invalidatepage\fR does not have to release all buffers, but it must
ensure that no dirty buffer is left outside \fIoffset\fR and that no I/O
is underway against any of the blocks which are outside the truncation
point.  Because the caller is about to free (and possibly reuse) those
blocks on-disk.