public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: zhanchengbin <zhanchengbin1@huawei.com>
To: Lukas Czerner <lczerner@redhat.com>
Cc: Theodore Ts'o <tytso@mit.edu>, <linux-ext4@vger.kernel.org>,
	<liuzhiqiang26@huawei.com>, linfeilong <linfeilong@huawei.com>
Subject: Re: [PATCH] misc/fsck.c: Processes may kill other processes.
Date: Mon, 10 Oct 2022 16:32:32 +0800	[thread overview]
Message-ID: <64352d65-dc3e-69ee-cd96-0440a32709d3@huawei.com> (raw)
In-Reply-To: <20221010071725.ghflyqxj7poqlwtq@fedora>



On 2022/10/10 15:17, Lukas Czerner wrote:
> On Sat, Oct 08, 2022 at 11:05:48AM +0800, zhanchengbin wrote:
>> If run the fsck -N command, processes don't execute, just show what
>> would be done. However, the pid whose value is -1 is added to the
>> instance_list list in the execute function,if the kill_all function
>> is called later, kill(-1, signum) is executed, Signals are sent to
>> all processes except the number one process and itself. Other
>> processes will be killed if they use the default signal processing
>> function.
>>
>> Signed-off-by: zhanchengbin <zhanchengbin1@huawei.com>
>> ---
>>   misc/fsck.c | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/misc/fsck.c b/misc/fsck.c
>> index 4efe10ec..faf7789d 100644
>> --- a/misc/fsck.c
>> +++ b/misc/fsck.c
>> @@ -546,6 +546,8 @@ static int kill_all(int signum)
>>   	for (inst = instance_list; inst; inst = inst->next) {
>>   		if (inst->flags & FLAG_DONE)
>>   			continue;
>> +		if (inst->pid == -1)
>> +			continue;
> 
> That works, but I think we can afford to be a little defensive here.
> Anything <= 0 is a bug and can have unexpected consequences if we
> actually call the kill().
> 
> 		if (inst->pid <= 0)
> 			continue

OK, I'll fix this and send the v2 version of the patch.

> 
> 
> Also as Darrick pointed out we need to send the patch to util-linux
> (disk-utils/fsck.c) as well if you haven't already.

I'll check and modify util-linux(disk-utils/fsck.c).

-zhanchengbin

> 
> -Lukas
> 
> 
>>   		kill(inst->pid, signum);
>>   		n++;
>>   	}
>> -- 
>> 2.27.0
>>
> 
> .
> 

      reply	other threads:[~2022-10-10  8:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08  3:05 [PATCH] misc/fsck.c: Processes may kill other processes zhanchengbin
2022-10-10  7:17 ` Lukas Czerner
2022-10-10  8:32   ` zhanchengbin [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=64352d65-dc3e-69ee-cd96-0440a32709d3@huawei.com \
    --to=zhanchengbin1@huawei.com \
    --cc=lczerner@redhat.com \
    --cc=linfeilong@huawei.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=liuzhiqiang26@huawei.com \
    --cc=tytso@mit.edu \
    /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