* Re: Possible 6.5 regression: Huge values for "commited memory"
[not found] ` <CAHk-=wjrEjaUw3oFVEYpF=AWAwrSM3sQTQHuPfFjFdQsvQxHeg@mail.gmail.com>
@ 2023-09-17 5:02 ` Helge Deller
2023-09-17 6:10 ` Greg Kroah-Hartman
0 siblings, 1 reply; 2+ messages in thread
From: Helge Deller @ 2023-09-17 5:02 UTC (permalink / raw)
To: Linus Torvalds, stable, Sasha Levin, Greg Kroah-Hartman
Cc: Linux PARISC, Linux Memory Management List,
Linux Kernel Mailing List, Linux Regressions, Andrew Morton,
Liam R. Howlett, Matthew Wilcox (Oracle), Bagas Sanjaya,
Michael Labiuk, Christoph Biedl
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
Thanks,
Helge
On 9/16/23 23:17, Linus Torvalds wrote:
> On Sat, 16 Sept 2023 at 12:31, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>>
>> Does the attached patch fix the problem?
>
> So while I didn't confirm the fix myself, I'm pretty sure that was it.
> Getting the return value wrong would cause an incorrect extra
> vm_acct_memory() call in the non-error case when VM_ACCOUNT is set
> (and mean the loss of one in the error case, but the error case never
> happens in practice).
>
> Which then causes 'vm_committed_as' to grow when it shouldn't, and
> causes exactly that "Committed_AS" in /proc/meminfo to be off.
>
> So here's the same patch, but now with a proper commit message etc.
>
> 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.
>
> Linus
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Possible 6.5 regression: Huge values for "commited memory"
2023-09-17 5:02 ` Possible 6.5 regression: Huge values for "commited memory" Helge Deller
@ 2023-09-17 6:10 ` Greg Kroah-Hartman
0 siblings, 0 replies; 2+ messages in thread
From: Greg Kroah-Hartman @ 2023-09-17 6:10 UTC (permalink / raw)
To: Helge Deller
Cc: Linus Torvalds, stable, Sasha Levin, Linux PARISC,
Linux Memory Management List, Linux Kernel Mailing List,
Linux Regressions, Andrew Morton, Liam R. Howlett,
Matthew Wilcox (Oracle), Bagas Sanjaya, Michael Labiuk,
Christoph Biedl
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-09-17 6:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1694366957@msgid.manchmal.in-ulm.de>
[not found] ` <ZQWUzwiKWLk79qbp@debian.me>
[not found] ` <CAHk-=wh29JJSVGyJM7ubxOs51-Nxp6YnmU9Bw1gdOk3rrQ_0mg@mail.gmail.com>
[not found] ` <CAHk-=wjrEjaUw3oFVEYpF=AWAwrSM3sQTQHuPfFjFdQsvQxHeg@mail.gmail.com>
2023-09-17 5:02 ` Possible 6.5 regression: Huge values for "commited memory" Helge Deller
2023-09-17 6:10 ` Greg Kroah-Hartman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox