From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Richard Palethorpe <rpalethorpe@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/2] madvise06: Fix segfault
Date: Fri, 11 Mar 2022 15:46:54 +0100 [thread overview]
Message-ID: <Yitg3pLd3F9Jum0c@pevik> (raw)
In-Reply-To: <YitAg8rGd++vHUlB@yuki>
Hi Cyril,
...
> > if (SAFE_CG_HAS(tst_cg, "memory.swappiness")) {
> > - SAFE_CG_PRINT(tst_cg, "memory.swappiness", "60");
> > + SAFE_CG_PRINT(tst_cg, "memory.swappiness", SWAPPINESS);
> > } else {
> > check_path("/proc/sys/vm/swappiness");
> > - SAFE_FILE_PRINTF("/proc/sys/vm/swappiness", "%d", 60);
> > }
> I'm not sure if we want to set the "/proc/sys/vm/swappiness"
> unconditinally in the .save_restore as previously we set it only if the
> cgroup was missing the swappines knob.
> So maybe we should go for a minimal fix here, just change the
> save_restore to match the new format and don't set the value there.
Make sense.
> > SAFE_CG_PRINTF(tst_cg, "cgroup.procs", "%d", getpid());
> > @@ -229,8 +229,8 @@ static struct tst_test test = {
> > .min_kver = "3.10.0",
> > .needs_tmpdir = 1,
> > .needs_root = 1,
> > - .save_restore = (const char * const[]) {
> > - "?/proc/sys/vm/swappiness",
> > + .save_restore = (const struct tst_path_val const[]) {
> > + {"?/proc/sys/vm/swappiness", SWAPPINESS},
> > NULL
> This has to be terminated by {} now.
Ah, thx!
Anyway, merged only minimal change with your Reviewed-by: tag.
Thanks!
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-03-11 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 12:01 [LTP] [PATCH 1/2] madvise06: Fix segfault Petr Vorel
2022-03-11 12:01 ` [LTP] [PATCH 2/2] madvise06: Move oom_score_adj initialization to struct tst_path_val Petr Vorel
2022-03-11 12:37 ` Cyril Hrubis
2022-03-14 3:37 ` Li Wang
2022-03-11 12:28 ` [LTP] [PATCH 1/2] madvise06: Fix segfault Cyril Hrubis
2022-03-11 14:46 ` Petr Vorel [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=Yitg3pLd3F9Jum0c@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.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 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.