Re: [PATCH 1/3] btrfs: unlock inode and extent on pages alloc failure in uring read

Hi Wenruo,

On 2026/8/5 12:49, Qu Wenruo wrote:
> The extra handling is only to unlock the inode and extent io tree.
>
> And neither the inode nor extent io tree is locked by the function
> itself, but btrfs_encoded_read().
>
> I do not believe this is the correct location to unlock inode/extent io
> tree.
>
> Move the unlock into the caller, as the caller is already doing such
> unlock after copy_to_user() failed.

Right, will move the unlock to the caller in v2.

Thanks,
Yang Xiuwei