locking rules for ->dirty_inode()

From: Nikita Danilov (Nikita@Namesys.COM)
Date: Fri Sep 20 2002 - 10:00:16 EST


Documentation/filesystems/Locking states that all super operations may
block, but __set_page_dirty_buffers() calls


under mapping->private_lock spin lock. This seems strange, because file
systems' ->dirty_inode() assume that they are allowed to block. For
example, ext3_dirty_inode() allocates memory in



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:30 EST