kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: ydroneaud@opteya.com (Yann Droneaud)
To: kernelnewbies@lists.kernelnewbies.org
Subject: File Descriptor allocation
Date: Thu, 26 Jan 2017 15:33:22 +0100	[thread overview]
Message-ID: <1485441202.13974.3.camel@opteya.com> (raw)
In-Reply-To: <CAPU=OMH20bjtEiFrc+54A2UHm7OP8y-m+RaqcEaMXrffP2Oz=Q@mail.gmail.com>

Hi,

Le jeudi 26 janvier 2017 ? 19:26 +0530, vish chopra a ?crit?:

> 
> i would like to know how a fd is allocated to a process?
> Flow chat of function calling, i.e which function are called during
> allocation of fd to a process.
> 

Have a look at get_unused_fd_flags() and fd_install()

(also anon_inode_getfd(), but you should probably not use it).

Regards.

-- 
Yann Droneaud
OPTEYA

      reply	other threads:[~2017-01-26 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 13:56 File Descriptor allocation vish chopra
2017-01-26 14:33 ` Yann Droneaud [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=1485441202.13974.3.camel@opteya.com \
    --to=ydroneaud@opteya.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).