From: Aristeu Rozanski <aris@ruivo.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Aristeu Rozanski <aris@redhat.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Muchun Song <muchun.song@linux.dev>,
David Hildenbrand <david@redhat.com>,
Vishal Moola <vishal.moola@gmail.com>
Subject: Re: [linux-next:master] [hugetlb] 003af997c8: libhugetlbfs-test.32/64bit.counters_sh.fail
Date: Wed, 17 Jul 2024 16:45:07 -0400 [thread overview]
Message-ID: <20240717204507.GJ844599@cathedrallabs.org> (raw)
In-Reply-To: <20240716154427.GI844599@cathedrallabs.org>
On Tue, Jul 16, 2024 at 11:44:27AM -0400, Aristeu Rozanski wrote:
> Taking a look on this.
So it looks like to be a timing issue. While spreading some code to figure out
exactly which exact sequence is causing the issue, it makes the error go away
in the 'counters' test. More specifically one of the sequences:
/* touched, shared mmap */
map(SL_TEST, 1, MAP_SHARED);
touch(SL_TEST, 1, MAP_SHARED);
unmap(SL_TEST, 1, MAP_SHARED);
fails because it's expecting:
HugePages_{Total,Free} = 1
HugePages_Surp = 0
but gets:
HugePages_{Total,Free} = 2
HugePages_Surp = 1
which seems caused by a surplus page taking too long to be freed, thus
timing making difference here.
I'm not sure as why it'd take longer with my patch applied but will keep
digging.
--
Aristeu
next prev parent reply other threads:[~2024-07-17 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 13:30 kernel test robot
2024-07-16 15:44 ` Aristeu Rozanski
2024-07-17 20:45 ` Aristeu Rozanski [this message]
2024-07-24 19:48 ` Aristeu Rozanski
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=20240717204507.GJ844599@cathedrallabs.org \
--to=aris@ruivo.org \
--cc=akpm@linux-foundation.org \
--cc=aris@redhat.com \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=muchun.song@linux.dev \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=vishal.moola@gmail.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