From: Li Wang <li.wang@linux.dev>
To: Andrea Cervesato <andrea.cervesato@suse.de>,
Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2 1/2] shell: add optional OOM protection
Date: Sat, 1 Aug 2026 20:04:58 +0800 [thread overview]
Message-ID: <am3g6oTHnfmiYORz@linux.dev> (raw)
In-Reply-To: <am3dJgE_4tMWnsh1@linux.dev>
> > + if [ "$TST_OOM_PROTECTION" = 1 -a "$_TST_OOM_PROTECTION" != 0 ]; then
> > + _tst_run_oom_protected "$@"
> > + fi
>
> In the C library, OOM protection for the LTP library and harness
> is enabled by default. But in such Shell implementation, we have to
> explicitly enable it via 'TST_OOM_PROTECTION=1'.
Say precisely: only protect LTP library not contains upper harness.
The upper harness can to be handled out from LTP.
See:
commit 8e5fe1d5f2 ("lib: enable OOM protection for ltp lib process")
> If we keep them consistent and remove the TST_OOM_PROTECTION
> variable, things will become easier I guess :).
--
Regards,
Li Wang
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-01 12:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 13:05 [LTP] [PATCH v2 0/2] OOM protection for shell tests Andrea Cervesato
2026-07-30 13:05 ` [LTP] [PATCH v2 1/2] shell: add optional OOM protection Andrea Cervesato
2026-07-30 14:10 ` [LTP] " linuxtestproject.agent
2026-07-31 13:03 ` [LTP] [PATCH v2 1/2] " Petr Vorel
2026-08-01 11:48 ` Li Wang
2026-08-01 12:04 ` Li Wang [this message]
2026-07-30 13:05 ` [LTP] [PATCH v2 2/2] memcg_stress: survive OOM by targeting the stressors Andrea Cervesato
2026-07-30 13:06 ` [LTP] [PATCH v2 0/2] OOM protection for shell tests Andrea Cervesato via ltp
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=am3g6oTHnfmiYORz@linux.dev \
--to=li.wang@linux.dev \
--cc=andrea.cervesato@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.