From: Benjamin Brunner <bbrunner@suse.com>
To: Coly Li <colyli@suse.de>, NeilBrown <neilb@suse.de>,
Franck Bui <fbui@suse.de>
Cc: linux-raid@vger.kernel.org,
mtkaczyk <mariusz.tkaczyk@linux.intel.com>,
Jes Sorensen <jsorensen@fb.com>
Subject: Re: [PATCH] mdadm/systemd: change KillMode from none to mixed in service files
Date: Tue, 7 Dec 2021 13:34:06 +0100 [thread overview]
Message-ID: <28a04276-d338-2db5-bb3d-49616e14206b@suse.com> (raw)
In-Reply-To: <dabe438e-3eca-8ad4-553e-ba8555d126bd@suse.de>
Hi,
On 05.12.21 14:42, Coly Li wrote:
> On 12/2/21 5:51 AM, NeilBrown wrote:
>> On Thu, 02 Dec 2021, Coly Li wrote:
>>> On 12/2/21 12:28 AM, Benjamin Brunner wrote:
>>>> Hi all,
>>>>
>>>> On 01.12.21 17:23, Coly Li wrote:
>>>>> On 12/2/21 12:08 AM, mtkaczyk wrote:
>>>>>> Hi Coly,
>>>>>>
>>>>>>> This patch changes KillMode in above listed service files from
>>>>>>> "none"
>>>>>>> to "mixed", to follow systemd recommendation and avoid potential
>>>>>>> unnecessary issue.
>>>>>> What about mdmonitor.service? Should we add it there too? Now it
>>>>>> is not
>>>>>> defined.
>>>>> It was overlooked when I did grep KillMode. Yes, I agree
>>>>> mdmonitor.service should have a KillMode key word as well.
>>>>>
>>>>> Let me post a v2 version.
>>>>>
>>>> JFYI, when KillMode is not set, it defaults to KillMode=control-group,
>>>> see https://www.freedesktop.org/software/systemd/man/systemd.kill.html.
>>>>
>>>> Therefore, it shouldn't be necessary to explicitly add it (as long as
>>>> control-group is working in case of mdmonitor.service, of course).
>>> Hi Benjamin,
>>>
>>> Please correct me if I am wrong, I see the difference of the KillMode
>>> is,
>>> -- KillMode=mixed stops the processes more gentally, it kill the main
>>> process with SIGTERM and the remaining processes with SIGKILL.
>>> -- KillMode=control-group kills all in-cgroup processes with SIGKILL,
>>> which I feel a bit cruel for the main process.
>> There is no point sending SIGTERM to a process which doesn't respond to
>> it. mdmon is the only mdadm service which handles SIGTERM. So it might
>> make sense to uise KillMode=mixed for that.
>> For anything else, SIGKILL via KillMode=control-group is perfectly
>> acceptable.
>
> Hi Neil,
>
> Thanks for the hint. So it seems remove the KillMode= lines from the
> systemd files might be best choice.
>
> Hi Benjamin,
>
> How do you think about removing the KillMode= lines to use SIGKILL as
> default action ?
>
From my PoV, this should be fine. To be on the safe side, I've added
Franck Bui, our systemd maintainer, to the list of recipients.
Franck, could you have a look as well, please?
Thanks,
Benjamin
> Thanks.
>
> Coly Li
>
--
Benjamin Brunner
Engineering Manager System Boot and Init
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nürnberg
Germany
HRB 36809, AG Nürnberg
Geschäftsführer: Ivo Totev
next prev parent reply other threads:[~2021-12-07 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 6:22 [PATCH] mdadm/systemd: change KillMode from none to mixed in service files Coly Li
2021-12-01 16:08 ` mtkaczyk
2021-12-01 16:23 ` Coly Li
2021-12-01 16:28 ` Benjamin Brunner
2021-12-01 16:43 ` Coly Li
2021-12-01 21:51 ` NeilBrown
2021-12-05 13:42 ` Coly Li
2021-12-07 12:34 ` Benjamin Brunner [this message]
2021-12-08 16:25 ` Franck Bui
2021-12-08 21:27 ` NeilBrown
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=28a04276-d338-2db5-bb3d-49616e14206b@suse.com \
--to=bbrunner@suse.com \
--cc=colyli@suse.de \
--cc=fbui@suse.de \
--cc=jsorensen@fb.com \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=neilb@suse.de \
/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