lkml.org 
[lkml]   [2021]   [Jul]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH 1/1] mm: introduce process_reap system call
Date
* Suren Baghdasaryan:

> On Wed, Jul 7, 2021 at 2:47 AM Florian Weimer <fweimer@redhat.com> wrote:
>>
>> * Suren Baghdasaryan:
>>
>> > The API is as follows,
>> >
>> > int process_reap(int pidfd, unsigned int flags);
>> >
>> > DESCRIPTION
>> > The process_reap() system call is used to free the memory of a
>> > dying process.
>> >
>> > The pidfd selects the process referred to by the PID file
>> > descriptor.
>> > (See pidofd_open(2) for further information)
>> >
>> > The flags argument is reserved for future use; currently, this
>> > argument must be specified as 0.
>> >
>> > RETURN VALUE
>> > On success, process_reap() returns 0. On error, -1 is returned
>> > and errno is set to indicate the error.
>>
>> I think the manual page should mention what it means for a process to be
>> “dying”, and how to move a process to this state.
>
> Thanks for the suggestion, Florian! Would replacing "dying process"
> with "process which was sent a SIGKILL signal" be sufficient?

That explains very clearly the requirement, but it raises the question
why this isn't an si_code flag for rt_sigqueueinfo, reusing the existing
system call.

Thanks,
Florian

\
 
 \ /
  Last update: 2021-07-08 07:41    [W:0.056 / U:5.396 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site