From: Pedro Falcato <pfalcato@suse.de>
To: Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org, david@kernel.org, ljs@kernel.org,
jannh@google.com, liam@infradead.org, willy@infradead.org,
paulmck@kernel.org, usama.arif@linux.dev, vbabka@kernel.org,
linux-fsdevel@vger.kernel.org, yi1.lai@intel.com,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] selftests/proc: use RSS in /proc/pid/smaps_rollup tearing tests
Date: Wed, 28 Oct 2026 19:42:02 +0000 [thread overview]
Message-ID: <auJO9al4lmAczLAu@pedro-suse.tail5790ac.ts.net> (raw)
In-Reply-To: <auHK3k-W4gfL_MhI@pedro-suse.tail5790ac.ts.net>
On Wed, Oct 28, 2026 at 10:14:19AM +0000, Pedro Falcato wrote:
> On Tue, Oct 27, 2026 at 10:13:12PM -0700, Suren Baghdasaryan wrote:
> > Pss metrics can be affected by map count even if VMA tree stays unchanged,
> > therefore test checking VMA tree integrity can't use them. Use Rss instead
> > and pre-populate the VMAs so that Rss changes if a VMA gets skipped or
> > double-counted.
> >
> > Fixes: ca5480fb53fa ("selftests/proc: add /proc/pid/smaps_rollup tearing tests")
> > Reported-by: kernel test robot <yi1.lai@intel.com>
> > Closes: https://lore.kernel.org/oe-lkp/202610271934.fd287c3f-lkp@intel.com
> > Signed-off-by: Suren Baghdasaryan <surenb@google.com>
>
> Reviewed-by: Pedro Falcato <pfalcato@suse.de>
Actually, now I'm wondering: isn't Rss also flaky if memory pressure occurs?
--
Pedro
next prev parent reply other threads:[~2026-10-28 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 5:13 Suren Baghdasaryan
2026-10-28 9:19 ` Lorenzo Stoakes (ARM)
2026-10-28 10:14 ` Pedro Falcato
2026-10-28 19:42 ` Pedro Falcato [this message]
2026-10-28 19:59 ` 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=auJO9al4lmAczLAu@pedro-suse.tail5790ac.ts.net \
--to=pfalcato@suse.de \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=paulmck@kernel.org \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=willy@infradead.org \
--cc=yi1.lai@intel.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®