From: Tang Yizhou <tangyeechou@gmail.com>
To: Cyril Hrubis <chrubis@suse.cz>, Tang Yizhou <yizhou.tang@shopee.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] perf_event_open03: Track SUnreclaim growth instead of MemAvailable
Date: Wed, 22 Jul 2026 13:40:11 +0800 [thread overview]
Message-ID: <60b5ffe7-dc56-44df-8ac3-be020e033795@gmail.com> (raw)
In-Reply-To: <al92s67_X0D7m01y@yuki.lan>
On 21/7/26 9:40 pm, Cyril Hrubis wrote:
> Hi!
>> - if ((sample > 5) || (diff_total > 100 * 1024))
>> - tst_res(TFAIL, "Likely kernel memory leak detected, total decrease: %ld kB", diff_total);
>> - else
>> + if ((sample > 5) || (diff_total > 100 * 1024)) {
>> + tst_res(TFAIL,
>> + "Likely kernel memory leak detected, SUnreclaim increased by %ld kB total",
>> + diff_total);
>> + tst_res(TINFO,
>> + "Unreclaimable slab can also grow due to memory activity from "
>> + "any other unrelated process. If this test fails, re-run it on "
>> + "an otherwise idle system and/or confirm with kmemleak "
>> + "(CONFIG_DEBUG_KMEMLEAK) before treating it as a real regression.");
>
> I wouldn't be that verbose here. Maybe something as:
>
> "Unreclaimable slab can grow due to unrelated
> reasons as well. You can rerun the test with
> CONFIG_DEBUG_KMEMLEAK to make sure the leak is
> real.
OK. Will update in v2.
--
Best Regards,
Yi
>
> Other than that:
>
> Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
>
>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-07-22 5:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 11:13 [LTP] [PATCH] perf_event_open03: Track SUnreclaim growth instead of MemAvailable Tang Yizhou via ltp
2026-07-14 12:15 ` [LTP] " linuxtestproject.agent
2026-07-21 7:54 ` [LTP] [PATCH] " Tang Yizhou
2026-07-21 13:32 ` Vlastimil Babka via ltp
2026-07-21 13:40 ` Cyril Hrubis
2026-07-22 5:40 ` Tang Yizhou [this message]
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=60b5ffe7-dc56-44df-8ac3-be020e033795@gmail.com \
--to=tangyeechou@gmail.com \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=yizhou.tang@shopee.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