.\" 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 "JOURNAL_CALLBACK_SET" "" "06 October 2005" "" ""

.SH NAME
journal_callback_set \- Register a callback function for this handle.
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void journal_callback_set  (handle_t * \fIhandle\fB, void (*\fIfunc\fB)
struct journal_callback *jcb, int error, struct journal_callback * \fIjcb\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIhandle\fB\fR
handle to attach the callback to.
.TP
\fB\fIfunc\fB\fR
function to callback.
.TP
\fB\fIjcb\fB\fR
structure with additional information required by \fBfunc\fR , and
some space for jbd internal information.
.SH "DESCRIPTION"
.PP
The function will be
called when the transaction that this handle is part of has been
committed to disk with the original callback data struct and the
error status of the journal as parameters.  There is no guarantee of
ordering between handles within a single transaction, nor between
callbacks registered on the same handle.
.PP
The caller is responsible for allocating the journal_callback struct.
This is to allow the caller to add as much extra data to the callback
as needed, but reduce the overhead of multiple allocations.  The caller
allocated struct must start with a struct journal_callback at offset 0,
and has the caller-specific data afterwards.