Commit:     e7ca2d41a029577a8cff453d1445951d4f96bfd8
Parent:     20420bba13bf79c86cab1e5bdfc4c938d9e44bc9
Author:     Joern Engel <[EMAIL PROTECTED]>
AuthorDate: Wed Feb 6 01:36:59 2008 -0800
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Wed Feb 6 10:41:03 2008 -0800

    Document I_SYNC and I_DATASYNC
    After some archeology (see I
    finally figured out what the three I_DIRTY bits do.  Maybe others would
    prefer less effort to reach this insight.
    Signed-off-by: Joern Engel <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
 include/linux/fs.h |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/include/linux/fs.h b/include/linux/fs.h
index ed289a9..e260d9a 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -1279,8 +1279,10 @@ struct super_operations {
  * Two bits are used for locking and completion notification, I_LOCK and 
- * I_DIRTY_SYNC                Inode itself is dirty.
- * I_DIRTY_DATASYNC    Data-related inode changes pending
+ * I_DIRTY_SYNC                Inode is dirty, but doesn't have to be written 
+ *                     fdatasync().  i_atime is the usual cause.
+ * I_DIRTY_DATASYNC    Inode is dirty and must be written on fdatasync(), f.e.
+ *                     because i_size changed.
  * I_DIRTY_PAGES       Inode has dirty pages.  Inode itself may be clean.
  * I_NEW               get_new_inode() sets i_state to I_LOCK|I_NEW.  Both
  *                     are cleared by unlock_new_inode(), called from iget().
@@ -1312,8 +1314,6 @@ struct super_operations {
  *                     purpose reduces latency and prevents some filesystem-
  *                     specific deadlocks.
- * Q: Why does I_DIRTY_DATASYNC exist?  It appears as if it could be replaced
  * Q: What is the difference between I_WILL_FREE and I_FREEING?
  * Q: igrab() only checks on (I_FREEING|I_WILL_FREE).  Should it also check on
  *    I_CLEAR?  If not, why?
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to