search for: btrfs_submit_direct

...May 7 02:09:21 caper kernel: [ 726.752573] [<ffffffffa016da3d>] find_parent_nodes+0x45d/0x6b0 [btrfs] May 7 02:09:21 caper kernel: [ 726.752684] [<ffffffffa016dd29>] btrfs_find_all_roots+0x99/0x100 [btrfs] May 7 02:09:21 caper kernel: [ 726.752792] [<ffffffffa0119620>] ? btrfs_submit_direct+0x190/0x190 [btrfs] May 7 02:09:21 caper kernel: [ 726.752901] [<ffffffffa0119620>] ? btrfs_submit_direct+0x190/0x190 [btrfs] May 7 02:09:21 caper kernel: [ 726.753012] [<ffffffffa016e977>] iterate_extent_inodes+0x177/0x2c0 [btrfs] May 7 02:09:21 caper kernel: [ 726.753123] [&l...

...node)->runtime_flags))) { + inode_dio_done(inode); + flags = DIO_LOCKING | DIO_SKIP_HOLES; + wakeup = false; } ret = __blockdev_direct_IO(rw, iocb, inode, BTRFS_I(inode)->root->fs_info->fs_devices->latest_bdev, iov, offset, nr_segs, btrfs_get_blocks_direct, NULL, btrfs_submit_direct, flags); + if (wakeup) inode_dio_done(inode); + if (rw == WRITE) + mutex_lock(&inode->i_mutex); return ret; } -- 1.7.11.7 -- 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...

The freeze rwsem is taken by sb_start_intwrite() and dropped during the commit_ or end_transaction(). In the async case, that happens in a worker thread. Tell lockdep the calling thread is releasing ownership of the rwsem and the async thread is picking it up. Josef and I worked out a more complicated solution that made the async commit thread join and potentially get a later transaction, but

V1->V2: Check to see if our current ppos is >= i_size after a short DIO read, just in case it was actually a short read and we need to just return. This is similar to what already happens in the write case. If we have a short read while doing O_DIRECT, instead of just returning, fallthrough and try to read the rest via buffered IO. BTRFS needs this because if we encounter a compressed or

Hi all - The following 9 patches add more error handling to the btrfs code: - Add btrfs_panic - Catch locking failures in {set,clear}_extent_bit - Push up set_extent_bit errors to callers - Push up lock_extent errors to callers - Push up clear_extent_bit errors to callers - Push up unlock_extent errors to callers - Make pin_down_extent return void - Push up btrfs_pin_extent errors to

Hi all - Here''s my current error handling patchset, against 3.1-rc8. Almost all of this patchset is preparing for actual error handling. Before we start in on that work, I''m trying to reduce the surface we need to worry about. It turns out that there is a ton of code that returns an error code but never actually reports an error. The patchset has grown to 65 patches. 46 of them