Re: [PATCH 3/4] btrfs: handle logged extent failure properly

Subject: Re: [PATCH 3/4] btrfs: handle logged extent failure properly
From: Johannes Thumshirn <Johannes.Thumshirn@xxxxxxx>
Date: Thu, 13 Feb 2020 11:16:57 +0000
Accept-language: en-US
Ironport-sdr: BCqE6mKFUAl3offPyi8XuKAUmt5fI0bozFDMuiaLOoT3hLeYh5KIT70Xg5vkBw1uQnL6F0CDFD ZkudnHKcOeiOBFc/ulEJNGrLFDIFoz3Mcnw3ZEYEOj2F0VFd8YBv3M7n2XpKy3YDXSqo/H1N1z Z95i+wFfOyNAMg+nikcazTpxr14R31bozuAtltB5fGwf8sP3WqFCKvGda6MPA1PSu2BU0FuX7P jnHVwYCdpGa+0PvbO+WjPLVGdh1ucBBOS7Yp/bAvqaZD+UfqpG0+fEDFTgiIo84eEpl/RfxCxR uOo=
References: <20200211214042.4645-1-josef@toxicpanda.com> <20200211214042.4645-4-josef@toxicpanda.com>
Wdcipoutbound: EOP-TRUE

Looks good,
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@xxxxxxx>

References:
- [PATCH 0/4] Error condition failure fixes
  - From: Josef Bacik
- [PATCH 3/4] btrfs: handle logged extent failure properly
  - From: Josef Bacik