public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Wang" <00107082@163.com>
To: "Suren Baghdasaryan" <surenb@google.com>
Cc: kent.overstreet@linux.dev, linux-kernel@vger.kernel.org
Subject: Re: Abnormal values show up in /proc/allocinfo
Date: Tue, 26 Nov 2024 09:14:50 +0800 (CST)	[thread overview]
Message-ID: <51c19b31.eaf.193660912f7.Coremail.00107082@163.com> (raw)
In-Reply-To: <CAJuCfpEP-xMzHonsE3uV1uYahXehR007B5QX9KjdZdHBWyrXwQ@mail.gmail.com>


Hi, 



At 2024-11-26 04:31:39, "Suren Baghdasaryan" <surenb@google.com> wrote:
>
>Hi David,
>Could you please check if you have this fix:
>
>ed265529d39a "mm/codetag: fix arg in pgalloc_tag_copy alloc_tag_sub"
>
>It was merged after v6.12-rc6 and it fixes an accounting bug inside
>pgalloc_tag_copy(), which is used during compaction.
>Thanks,
>Suren.
>
>
>https://lore.kernel.org/all/20240906042108.1150526-3-yuzhao@google.com/
>https://lore.kernel.org/all/20241022232440.334820-1-souravpanda@google.com/


No, ed265529d39a is not in 6.12.0; It is now in Linus' tree.
I will pull the code and make some tests.

Will update later.

Thanks~
David

>
>> > >Thanks,
>> > >Suren.
>> > >
>> > >>
>> > >>
>> > >> Thanks
>> > >> David
>> > >>
>> > >>
>> > >>
>> > >>

  reply	other threads:[~2024-11-26  1:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-24  7:43 Abnormal values show up in /proc/allocinfo David Wang
2024-11-25  0:35 ` Suren Baghdasaryan
2024-11-25  1:01   ` David Wang
2024-11-25 10:09   ` David Wang
2024-11-25 17:31     ` Suren Baghdasaryan
2024-11-25 20:31       ` Suren Baghdasaryan
2024-11-26  1:14         ` David Wang [this message]
2024-11-26  7:16           ` David Wang
2024-11-26 17:10             ` Suren Baghdasaryan
2024-11-27  9:44               ` David Wang
2024-11-28  8:34                 ` David Wang
2024-11-28 18:46                   ` Suren Baghdasaryan
2024-11-28 19:58                     ` Suren Baghdasaryan

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=51c19b31.eaf.193660912f7.Coremail.00107082@163.com \
    --to=00107082@163.com \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=surenb@google.com \
    /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