From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v1] cgroup_fj_stress: Avoid killall
Date: Wed, 6 Nov 2019 18:12:01 +0100 [thread overview]
Message-ID: <20191106171201.GA22894@dell5510> (raw)
In-Reply-To: <1572961744.4619.20.camel@suse.de>
Hi Clemens,
> > I wonder if we also want to kill cgroup_fj_proc this way (see
> > cgroup_fj_common.sh).
> I'm not sure if I understand you. We do kill cgroup_fj_proc this way.
> The `killall -9 cgroup_fj_proc` call in cgrouip_fj_common.sh looks for
> me like a cleaner and there is no `wait` or similar afterwards, so I
> would guess we are not facing the problem here. And I would keep
> killall here.
> As far as I can see, all other `cgroup_fj_proc&` calls already kill
> them separately.
OK, merged :).
Thanks!
> > I guess you're not planning to create minimal reproducer to prove the
> > problem of
> > left processes after killall, are you?
> Sure nice idea, I can give it a try. But not within this patchset.
Thanks!
Kind regards,
Petr
prev parent reply other threads:[~2019-11-06 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 11:20 [LTP] [PATCH v1] cgroup_fj_stress: Avoid killall Clemens Famulla-Conrad
2019-11-05 13:20 ` Petr Vorel
2019-11-05 13:49 ` Clemens Famulla-Conrad
2019-11-06 17:12 ` 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=20191106171201.GA22894@dell5510 \
--to=pvorel@suse.cz \
--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