From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Helge Deller <deller@gmx.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
Linux PARISC <linux-parisc@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Michael Labiuk <michael.labiuk@virtuozzo.com>,
Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
Subject: Re: Possible 6.5 regression: Huge values for "commited memory"
Date: Sun, 17 Sep 2023 08:10:52 +0200 [thread overview]
Message-ID: <2023091742-static-unedited-b414@gregkh> (raw)
In-Reply-To: <3ee4b922-7686-ec20-f280-48c06bff09cf@gmx.de>
On Sun, Sep 17, 2023 at 07:02:50AM +0200, Helge Deller wrote:
> Greg & Sasha,
>
> can you please queue-up this upstream patch for kernel v6.5-stable ?
>
> commit 3cec50490969afd4a76ccee441f747d869ccff77
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Sat Sep 16 12:31:42 2023 -0700
>
> vm: fix move_vma() memory accounting being off
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2023-09-17 6:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 17:48 Possible 6.5 regression: Huge values for "commited memory" Christoph Biedl
2023-09-12 19:32 ` Helge Deller
2023-09-13 0:25 ` Bagas Sanjaya
2023-09-15 16:27 ` Michael Labiuk
2023-09-16 11:43 ` Bagas Sanjaya
2023-09-16 19:31 ` Linus Torvalds
2023-09-16 21:17 ` Linus Torvalds
2023-09-16 22:20 ` Michael Labiuk
2023-09-16 22:25 ` Linus Torvalds
2023-09-17 5:02 ` Helge Deller
2023-09-17 6:10 ` Greg Kroah-Hartman [this message]
2023-09-21 7:09 ` Christoph Biedl
2023-09-16 22:35 ` Liam R. Howlett
2023-09-17 10:13 ` Bagas Sanjaya
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=2023091742-static-unedited-b414@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=deller@gmx.de \
--cc=linux-kernel.bfrz@manchmal.in-ulm.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=michael.labiuk@virtuozzo.com \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.