Messages in this thread | | | From | Nikita Danilov <> | Date | Fri, 20 Sep 2002 19:00:16 +0400 | Subject | locking rules for ->dirty_inode() |
| |
Hello,
Documentation/filesystems/Locking states that all super operations may block, but __set_page_dirty_buffers() calls
__mark_inode_dirty()->s_op->dirty_inode()
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
ext3_journal_start()->journal_start()->new_handle()->...
Nikita.
- 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/
| |