1<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>__mark_inode_dirty</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Linux Filesystems API"><link rel="up" href="other_functions.html" title="Other Functions"><link rel="prev" href="API-inode-congested.html" title="inode_congested"><link rel="next" href="API-writeback-inodes-sb-nr.html" title="writeback_inodes_sb_nr"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"><span class="phrase">__mark_inode_dirty</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="API-inode-congested.html">Prev</a> </td><th width="60%" align="center">Other Functions</th><td width="20%" align="right"> <a accesskey="n" href="API-writeback-inodes-sb-nr.html">Next</a></td></tr></table><hr></div><div class="refentry"><a name="API---mark-inode-dirty"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>__mark_inode_dirty — 
2     internal function
3 </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="funcsynopsis"><table border="0" class="funcprototype-table" summary="Function synopsis" style="cellspacing: 0; cellpadding: 0;"><tr><td><code class="funcdef">void <b class="fsfunc">__mark_inode_dirty </b>(</code></td><td>struct inode * <var class="pdparam">inode</var>, </td></tr><tr><td> </td><td>int <var class="pdparam">flags</var><code>)</code>;</td></tr></table><div class="funcprototype-spacer"> </div></div></div><div class="refsect1"><a name="id-1.3.7.67.5"></a><h2>Arguments</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><em class="parameter"><code>inode</code></em></span></dt><dd><p>
4     inode to mark
5    </p></dd><dt><span class="term"><em class="parameter"><code>flags</code></em></span></dt><dd><p>
6     what kind of dirty (i.e. I_DIRTY_SYNC)
7     Mark an inode as dirty. Callers should use mark_inode_dirty or
8     mark_inode_dirty_sync.
9    </p></dd></dl></div></div><div class="refsect1"><a name="id-1.3.7.67.6"></a><h2>Description</h2><p>
10   Put the inode on the super block's dirty list.
11   </p><p>
12
13   CAREFUL! We mark it dirty unconditionally, but move it onto the
14   dirty list only if it is hashed or if it refers to a blockdev.
15   If it was not hashed, it will never be added to the dirty list
16   even if it is later hashed, as it will have been marked dirty already.
17   </p><p>
18
19   In short, make sure you hash any inodes _before_ you start marking
20   them dirty.
21   </p><p>
22
23   Note that for blockdevs, inode-&gt;dirtied_when represents the dirtying time of
24   the block-special inode (/dev/hda1) itself.  And the -&gt;dirtied_when field of
25   the kernel-internal blockdev inode represents the dirtying time of the
26   blockdev's pages.  This is why for I_DIRTY_PAGES we always use
27   page-&gt;mapping-&gt;host, so the page-dirtying time is recorded in the internal
28   blockdev inode.
29</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="API-inode-congested.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="other_functions.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="API-writeback-inodes-sb-nr.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"><span class="phrase">inode_congested</span> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> <span class="phrase">writeback_inodes_sb_nr</span></td></tr></table></div></body></html>
30