From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michael Labiuk <michael.labiuk@virtuozzo.com>,
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>
Subject: Re: Possible 6.5 regression: Huge values for "commited memory"
Date: Thu, 21 Sep 2023 09:09:19 +0200 [thread overview]
Message-ID: <1695279990@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <CAHk-=wjrEjaUw3oFVEYpF=AWAwrSM3sQTQHuPfFjFdQsvQxHeg@mail.gmail.com>
[
A tad late in the party, I know. The box I had encoutered this isn't
quite on 24/7, and reproduction took some time.
]
Linus Torvalds wrote...
> I haven't pushed it out (because it would be lovely to get a
> "Tested-by" for it, and that will make the commit ID change), but I'll
> probably do so later today, with or without confirmation, because it
> does seem to be the problem.
Confirmed this solves the issue here, too. Tested on 6.6-rc2.
Christoph
next prev parent reply other threads:[~2023-09-21 20:00 UTC|newest]
Thread overview: 12+ 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
[not found] ` <ZQWUzwiKWLk79qbp@debian.me>
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
2023-09-21 7:09 ` Christoph Biedl [this message]
2023-09-16 22:35 ` Liam R. Howlett
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=1695279990@msgid.manchmal.in-ulm.de \
--to=linux-kernel.bfrz@manchmal.in-ulm.de \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).