Re: [PATCH] btrfs: Fix wrong first_key parameter in replace_path

2018-04-23 Thread David Sterba
On Mon, Apr 23, 2018 at 05:20:06PM +0300, Nikolay Borisov wrote: > On 23.04.2018 17:16, David Sterba wrote: > > On Mon, Apr 23, 2018 at 05:32:04PM +0800, Qu Wenruo wrote: > >> Commit 581c1760415c ("btrfs: Validate child tree block's level and first > >> key") introduced new @first_key parameter for

Re: [PATCH] btrfs: Fix wrong first_key parameter in replace_path

2018-04-23 Thread Nikolay Borisov
On 23.04.2018 17:16, David Sterba wrote: > On Mon, Apr 23, 2018 at 05:32:04PM +0800, Qu Wenruo wrote: >> Commit 581c1760415c ("btrfs: Validate child tree block's level and first >> key") introduced new @first_key parameter for read_tree_block(), however >> caller in replace_path() is parasing wro

Re: [PATCH] btrfs: Fix wrong first_key parameter in replace_path

2018-04-23 Thread David Sterba
On Mon, Apr 23, 2018 at 05:32:04PM +0800, Qu Wenruo wrote: > Commit 581c1760415c ("btrfs: Validate child tree block's level and first > key") introduced new @first_key parameter for read_tree_block(), however > caller in replace_path() is parasing wrong key to read_tree_block(). > > It should use

[PATCH] btrfs: Fix wrong first_key parameter in replace_path

2018-04-23 Thread Qu Wenruo
Commit 581c1760415c ("btrfs: Validate child tree block's level and first key") introduced new @first_key parameter for read_tree_block(), however caller in replace_path() is parasing wrong key to read_tree_block(). It should use parameter @first_key other than @key. Normally it won't expose probl