From: xuyang2018.jy@fujitsu.com <xuyang2018.jy@fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] syscalls/mallinfo01 test is broken
Date: Thu, 13 May 2021 02:27:40 +0000 [thread overview]
Message-ID: <609C8EBC.80409@fujitsu.com> (raw)
In-Reply-To: <YJvftrFCueG3TXPf@yuki>
Hi Cyril, Martin
> Hi!
>> the mallinfo01 test is failing on some of our test machines because it
>> makes wrong assumptions about how malloc() and free() will change the
>> number of free chunks (ordblks). I recommend we remove the test from
>> runfiles before the upcoming release and fix it later because part of
>> the test scenario needs major redesign.
>
> I've started some pre-release testruns and I've seen some failures as
> well. I guess that removing it from runtest file and fixing it after
> release sounds sane at this point.
This case fails because malloc uses fastbin blocks.
So the fix has two ways
1) disable fastbin by using mallopt(M_MXFAST, 0)
2) use another mallinfo struct info3 to get free chunks, so compare
info3 and info2 ordblks member.
Best Regards
Yang Xu
>
next prev parent reply other threads:[~2021-05-13 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 14:17 [LTP] syscalls/mallinfo01 test is broken Martin Doucha
2021-05-12 14:01 ` Cyril Hrubis
2021-05-13 2:27 ` xuyang2018.jy [this message]
2021-05-13 8:05 ` Cyril Hrubis
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=609C8EBC.80409@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=ltp@lists.linux.it \
/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