Re: [PATCH 01/17] btrfs: reada: Fix in-segment calculation for reada

[Greg KH <gregkh@linuxfoundation.org>]

On Thu, May 05, 2016 at 11:43:38AM +0200, David Sterba wrote:
> From: Zhao Lei <zhaolei@cn.fujitsu.com>
> 
> reada_zone->end is end pos of segment:
>  end = start + cache->key.offset - 1;
> 
> So we need to use "<=" in condition to judge is a pos in the
> segment.
> 
> The problem happened rearly, because logical pos rarely pointed
> to last 4k of a blockgroup, but we need to fix it to make code
> right in logic.
> 
> Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
>  fs/btrfs/reada.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Can you put the number of the commit in Linus's tree _in_ the patch
itself somewhere, either in the format that I use for when I do commits
to the stable branch (first line of the changelog text), or in the
signed-off-by: area like git cherry-pick does?

This way, as a list in patch 0/X separate from the commits and even the
descriptions, is pretty impossible to easily match up.

Can you redo this series and resend it with that fix?

thanks,

greg k-h