On 10/23/24 15:11, Shivam Chaudhary wrote:
On 24/10/24 2:15 AM, Shuah Khan wrote:
On 10/22/24 14:42, Shivam Chaudhary wrote:
This test verifies the correct behavior of the fork() system call,
which creates a child process by duplicating the parent process.
The test checks the following:
- The child PID returned by fork() is present in /proc.
- The child PID is different from the parent PID.
- The memory allocated to a variable in the child process is independent
of the parent process.
Short log should incude the subsystem:
e.g: selftests: add test for fork() syscall
In anycase, I don't see any value to adding this test.
fork() is a heavily used system call.
Thanks for responding Shuah,
Yes, you are correct that fork() is a heavily used syscall, that is why my concern is that
it could fail millions of other program that depends on fork() if any error or regression
occurs in the future. In my opinion, that is why we should test it every way possible.
Sorry. I don't see any value in adding this test.
thanks,
-- Shuah
