Subject: Re: [PATCH] mm/mmap: Fix vma_merge() offset when expanding the next vma

From: David Hildenbrand <[email-masked]>
Date: Tue, 31 Jan 2023 15:29:59 +0100

On 31.01.23 15:24, Liam R. Howlett wrote:
> * David Hildenbrand <[email-masked]> [230131 03:35]:
>> On 30.01.23 20:57, Liam R. Howlett wrote:
>>> The vm_pgoff was being set incorrectly when expanding the next VMA to a
>>> lower address.  Fix the issue by using the mid->vm_pgoff value for this
>>> merge case (aka case 8).  Note that this does not change case 3's
>>> vm_pgoff as next and mid are the same VMA.
>>>
>>> Reported-by: Sanan Hasanov <[email-masked]>
>>> Link: https://lore.kernel.org/linux-mm/[email-masked]/
>>> Cc: Matthew Wilcox <[email-masked]>
>>> Cc: David Hildenbrand <[email-masked]>
>>> Cc: Hugh Dickins <[email-masked]>
>>
>> Fixes: ?
> 
> Fixes: (soon to be invalid git id :) ("mm/mmap: remove __vma_adjust()")

Ah, right, upstream was not affected ... :)

... so this should be squashed into that commit instead as long as it 
doesn't have a stable ID.

-- 
Thanks,

David / dhildenb