From: Linus Torvalds <torvalds@linux-foundation.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
lstoakes@gmail.com, regressions@lists.linux.dev,
linux-mm@kvack.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, Jiri Slaby <jirislaby@kernel.org>,
Fabian Vogt <fvogt@suse.com>,
stable@vger.kernel.org
Subject: Re: [PATCH for v6.3 regression] mm/mremap: fix vm_pgoff in vma_merge() case 3
Date: Thu, 27 Apr 2023 19:53:48 -0700 [thread overview]
Message-ID: <CAHk-=whwoKFbrCGXW9uwX3SPOezLdOKstuLAju1KTi5Ryq+ZcQ@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wgdGzy6-3jzN6Kvtz1QxStTZBZPz1zy9i4gM9nbe5FGbA@mail.gmail.com>
Hi Vlastimil,
On Thu, Apr 27, 2023 at 8:12 AM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Ack. It's in my tree as commit 7e7757876f25 right now (not pushed out
> yet, will do the usual build tests and look around for other things
> pending).
Gaah. I just merged Andrew's MM tree, and while it had a lot of small
conflicts (and the ext4 ones were annoying semantic ones), the only
one that was in *confusing* code was the one introduced by this
one-liner fix.
I'm pretty sure I did the right thing, particularly given your other
patch for the mm tree, but please humor me and take a look at it?
That 'vma_merge()' function is the function from hell.
I haven't pushed out yet because it's still going through my build
tests, but it should be out soon.
Linus
next prev parent reply other threads:[~2023-04-28 2:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 14:09 Vlastimil Babka
2023-04-27 14:15 ` Vlastimil Babka
2023-04-27 14:27 ` Greg KH
2023-04-27 14:39 ` Vlastimil Babka
2023-04-27 15:12 ` Linus Torvalds
2023-04-28 2:53 ` Linus Torvalds [this message]
2023-04-28 7:13 ` Vlastimil Babka
2023-04-28 7:36 ` Greg KH
2023-04-28 6:15 ` Jiri Slaby
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='CAHk-=whwoKFbrCGXW9uwX3SPOezLdOKstuLAju1KTi5Ryq+ZcQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=fvogt@suse.com \
--cc=greg@kroah.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=patches@lists.linux.dev \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
/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