From: varyani.nitin1@gmail.com (Nitin Varyani)
To: kernelnewbies@lists.kernelnewbies.org
Subject: fork
Date: Mon, 18 Apr 2016 12:18:00 +0530 [thread overview]
Message-ID: <CAKfJ7K+ZFvYdFRefFn3=orALwOAmT2H6N6jdOf_z4E_+YVPSeQ@mail.gmail.com> (raw)
Linux kernel development by Robert Love describes the fork process as
fork() -> clone() -> do_fork() -> copy_process()
I am unable to find the clone() system call in linux 3.13.
Can someone explain the proper flow of fork() system call initiated by the
user?
Where can I find the libc implementation for fork()? I want the code of all
the functions involved in fork.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160418/248505f9/attachment.html
next reply other threads:[~2016-04-18 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 6:48 Nitin Varyani [this message]
2016-04-18 7:12 ` fork Alex Wilson
2016-04-18 8:18 ` fork Cihangir Akturk
2020-01-09 10:35 Fork Christophe DUMONT
2020-01-09 10:47 ` Fork Valentin Vidić
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='CAKfJ7K+ZFvYdFRefFn3=orALwOAmT2H6N6jdOf_z4E_+YVPSeQ@mail.gmail.com' \
--to=varyani.nitin1@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).