From: David Wang <00107082@163.com>
To: surenb@google.com, kent.overstreet@linux.dev
Cc: linux-kernel@vger.kernel.org
Subject: Abnormal values show up in /proc/allocinfo
Date: Sun, 24 Nov 2024 15:43:18 +0800 [thread overview]
Message-ID: <20241124074318.399027-1-00107082@163.com> (raw)
Hi,
I am running 6.12.0 for a week, and today I notice several strange
items in /proc/allocinfo:
-4096 18446744073709551615 mm/filemap.c:3787 func:do_read_cache_folio
-1946730496 18446744073709076340 mm/filemap.c:1952 func:__filemap_get_folio
-903294976 18446744073709331085 mm/readahead.c:263 func:page_cache_ra_unbounded
-353054720 18446744073709465421 mm/shmem.c:1769 func:shmem_alloc_folio
10547565210 0 mm/compaction.c:1880 func:compaction_alloc
-156487680 18446744073709513411 mm/memory.c:1064 func:folio_prealloc
-2422685696 18446744073708960140 mm/memory.c:1062 func:folio_prealloc
-2332479488 18446744073708982163 fs/btrfs/extent_io.c:635 [btrfs] func:btrfs_alloc_page_array
some values are way too large, seems like corrupted/uninitialized, and values for compaction_alloc
are inconsistent: non-zero size with zero count.
I do not know when those data became this strange, and I have not reboot my system yet.
Do you guys need extra information before I reboot my system and started to try reproducing?
Thanks
David
next reply other threads:[~2024-11-24 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 7:43 David Wang [this message]
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
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=20241124074318.399027-1-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
all inboxes | Powered by JetHome®