On Wed, Sep 18, 2019 at 01:08:52PM +0100, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> Some of the self tests create a test inode, setup some extents and then do
> calls to btrfs_get_extent() to test that the corresponding extent maps
> exist and are correct. However btrfs_get_extent(), s
On 2019/9/18 下午8:27, Filipe Manana wrote:
> On Wed, Sep 18, 2019 at 1:22 PM Qu Wenruo wrote:
>>
>>
>>
>> On 2019/9/18 下午8:08, fdman...@kernel.org wrote:
>>> From: Filipe Manana
>>>
>>> Some of the self tests create a test inode, setup some extents and then do
>>> calls to btrfs_get_extent() to
On Wed, Sep 18, 2019 at 1:22 PM Qu Wenruo wrote:
>
>
>
> On 2019/9/18 下午8:08, fdman...@kernel.org wrote:
> > From: Filipe Manana
> >
> > Some of the self tests create a test inode, setup some extents and then do
> > calls to btrfs_get_extent() to test that the corresponding extent maps
> > exist
On 2019/9/18 下午8:08, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> Some of the self tests create a test inode, setup some extents and then do
> calls to btrfs_get_extent() to test that the corresponding extent maps
> exist and are correct. However btrfs_get_extent(), since the 5.2 merge
From: Filipe Manana
Some of the self tests create a test inode, setup some extents and then do
calls to btrfs_get_extent() to test that the corresponding extent maps
exist and are correct. However btrfs_get_extent(), since the 5.2 merge
window, now errors out when it finds a regular or prealloc e
