.\" 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 "MARK_BUFFER_DIRTY" "9" "09 October 2005" "" ""

.SH NAME
mark_buffer_dirty \- mark a buffer_head as needing writeout
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void fastcall mark_buffer_dirty  (struct buffer_head * \fIbh\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIbh\fB\fR
the buffer_head to mark dirty
.SH "DESCRIPTION"
.PP
\fBmark_buffer_dirty\fR will set the dirty bit against the buffer, then set its
backing page dirty, then tag the page as dirty in its address_space's radix
tree and then attach the address_space's inode to its superblock's dirty
inode list.
.PP
\fBmark_buffer_dirty\fR is atomic.  It takes bh->b_page->mapping->private_lock,
mapping->tree_lock and the global inode_lock.