Re: [PATCH] btrfs: Handle btrfs_reloc_clone_csums error correctly to avoid deadlock

2017-02-20 Thread Qu Wenruo
At 02/20/2017 09:43 PM, Filipe Manana wrote: On Mon, Feb 20, 2017 at 12:31 AM, Qu Wenruo wrote: At 02/17/2017 11:25 PM, Filipe Manana wrote: On Fri, Feb 17, 2017 at 12:37 AM, Qu Wenruo wrote: In case of an error the endio handler is

Re: [PATCH] btrfs: Handle btrfs_reloc_clone_csums error correctly to avoid deadlock

2017-02-20 Thread Filipe Manana
On Mon, Feb 20, 2017 at 12:31 AM, Qu Wenruo wrote: > > > At 02/17/2017 11:25 PM, Filipe Manana wrote: >> >> On Fri, Feb 17, 2017 at 12:37 AM, Qu Wenruo >> wrote: >>> >>> >>> >>> At 02/16/2017 06:03 PM, Filipe Manana wrote: On Thu,

Re: [PATCH] btrfs: Handle btrfs_reloc_clone_csums error correctly to avoid deadlock

2017-02-19 Thread Qu Wenruo
At 02/17/2017 11:25 PM, Filipe Manana wrote: On Fri, Feb 17, 2017 at 12:37 AM, Qu Wenruo wrote: At 02/16/2017 06:03 PM, Filipe Manana wrote: On Thu, Feb 16, 2017 at 12:39 AM, Qu Wenruo wrote: At 02/15/2017 11:59 PM, Filipe Manana

Re: [PATCH] btrfs: Handle btrfs_reloc_clone_csums error correctly to avoid deadlock

2017-02-17 Thread Filipe Manana
On Fri, Feb 17, 2017 at 12:37 AM, Qu Wenruo wrote: > > > At 02/16/2017 06:03 PM, Filipe Manana wrote: >> >> On Thu, Feb 16, 2017 at 12:39 AM, Qu Wenruo >> wrote: >>> >>> >>> >>> At 02/15/2017 11:59 PM, Filipe Manana wrote: On Wed,

Re: [PATCH] btrfs: Handle btrfs_reloc_clone_csums error correctly to avoid deadlock

2017-02-16 Thread Qu Wenruo
At 02/16/2017 06:03 PM, Filipe Manana wrote: On Thu, Feb 16, 2017 at 12:39 AM, Qu Wenruo wrote: At 02/15/2017 11:59 PM, Filipe Manana wrote: On Wed, Feb 15, 2017 at 8:49 AM, Qu Wenruo wrote: If run btrfs/125 with nospace_cache or

Re: [PATCH] btrfs: Handle btrfs_reloc_clone_csums error correctly to avoid deadlock

2017-02-16 Thread Filipe Manana
On Thu, Feb 16, 2017 at 12:39 AM, Qu Wenruo wrote: > > > At 02/15/2017 11:59 PM, Filipe Manana wrote: >> >> On Wed, Feb 15, 2017 at 8:49 AM, Qu Wenruo >> wrote: >>> >>> If run btrfs/125 with nospace_cache or space_cache=v2 mount option, >>> btrfs

Re: [PATCH] btrfs: Handle btrfs_reloc_clone_csums error correctly to avoid deadlock

2017-02-15 Thread Qu Wenruo
At 02/15/2017 11:59 PM, Filipe Manana wrote: On Wed, Feb 15, 2017 at 8:49 AM, Qu Wenruo wrote: If run btrfs/125 with nospace_cache or space_cache=v2 mount option, btrfs will block with the following backtrace: Call Trace: __schedule+0x2d4/0xae0 schedule+0x3d/0x90

Re: [PATCH] btrfs: Handle btrfs_reloc_clone_csums error correctly to avoid deadlock

2017-02-15 Thread Filipe Manana
On Wed, Feb 15, 2017 at 8:49 AM, Qu Wenruo wrote: > If run btrfs/125 with nospace_cache or space_cache=v2 mount option, > btrfs will block with the following backtrace: > > Call Trace: > __schedule+0x2d4/0xae0 > schedule+0x3d/0x90 >

[PATCH] btrfs: Handle btrfs_reloc_clone_csums error correctly to avoid deadlock

2017-02-15 Thread Qu Wenruo
If run btrfs/125 with nospace_cache or space_cache=v2 mount option, btrfs will block with the following backtrace: Call Trace: __schedule+0x2d4/0xae0 schedule+0x3d/0x90 btrfs_start_ordered_extent+0x160/0x200 [btrfs] ? wake_atomic_t_function+0x60/0x60 btrfs_run_ordered_extent_work+0x25/0x40