From: David Hildenbrand <david@redhat.com>
To: "Liam R. Howlett" <Liam.Howlett@Oracle.com>,
maple-tree@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org,
Sanan Hasanov <sanan.hasanov@knights.ucf.edu>,
Matthew Wilcox <willy@infradead.org>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH] mm/mmap: Fix vma_merge() offset when expanding the next vma
Date: Tue, 31 Jan 2023 15:29:59 +0100 [thread overview]
Message-ID: <72dfedd2-a26a-17f4-87c2-3d71ab3f55b4@redhat.com> (raw)
In-Reply-To: <20230131142452.sfrmubta4ojejct2@revolver>
On 31.01.23 15:24, Liam R. Howlett wrote:
> * David Hildenbrand <david@redhat.com> [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 <sanan.hasanov@knights.ucf.edu>
>>> Link: https://lore.kernel.org/linux-mm/IA1PR07MB983017D2FBA174D2FF78CEB6ABCE9@IA1PR07MB9830.namprd07.prod.outlook.com/
>>> Cc: Matthew Wilcox <willy@infradead.org>
>>> Cc: David Hildenbrand <david@redhat.com>
>>> Cc: Hugh Dickins <hughd@google.com>
>>
>> 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
next prev parent reply other threads:[~2023-01-31 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 19:57 Liam R. Howlett
2023-01-31 8:35 ` David Hildenbrand
2023-01-31 14:24 ` Liam R. Howlett
2023-01-31 14:29 ` David Hildenbrand [this message]
2023-01-31 21:07 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=72dfedd2-a26a-17f4-87c2-3d71ab3f55b4@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=maple-tree@lists.infradead.org \
--cc=sanan.hasanov@knights.ucf.edu \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox