I have started looking into Btrfs data structures and trying to understand its code flow. The Btrfs worker thread relating to metadata end-io (btrfs-end-io-met) seems to have preempt count set to 1 which means that it should be run in atomic context. I found this while looking into the checksumming code (csum_tree_block) called from btrfs_readpage_end_io_hook. Please let me know if I am correct in my understanding and what is the reason for having it non-preemptible? Thanks, Aayush -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html