From: loris@draios.com (Loris Degioanni)
To: kernelnewbies@lists.kernelnewbies.org
Subject: fd type from number
Date: Mon, 18 Aug 2014 17:46:16 -0700 [thread overview]
Message-ID: <53F29E58.5060202@draios.com> (raw)
In-Reply-To: <CAPDOMVirn+wtoKBTTywsCEs8K-iKBg6wBz-z6Q7-zMWPTHsZRw@mail.gmail.com>
I'm looking for an efficient way to determine the type of an fd (file,
socket...) given its number, from a kernel module.
The closest thing I found by looking at the kernel sources is
sockfd_lookup(), which works but is limited to telling me if the fd is a
socket or not.
Is there something else I can look at?
Thank you in advance,
Loris
next prev parent reply other threads:[~2014-08-19 0:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 16:25 TCP/UDP Nick Krause
2014-08-18 16:51 ` TCP/UDP Afonso Bordado
2014-08-18 16:54 ` TCP/UDP Nick Krause
2014-08-18 16:57 ` TCP/UDP Valdis.Kletnieks at vt.edu
2014-08-18 17:13 ` TCP/UDP Nick Krause
2014-08-18 17:21 ` TCP/UDP Nick Krause
2014-08-18 17:26 ` TCP/UDP Manish Katiyar
2014-08-18 17:29 ` TCP/UDP Nick Krause
2014-08-19 2:06 ` one thing at a time Rik van Riel
2014-08-19 2:55 ` Nick Krause
2014-08-19 2:59 ` Nick Krause
2014-08-19 4:25 ` Nick Krause
2014-08-19 6:29 ` Jason Ball
2014-08-19 12:13 ` Greg Freemyer
2014-08-19 16:41 ` Nick Krause
2014-08-18 17:31 ` TCP/UDP Denis Kirjanov
2014-08-18 17:33 ` TCP/UDP Nick Krause
2014-08-18 19:43 ` TCP/UDP Nick Krause
2014-08-19 0:46 ` Loris Degioanni [this message]
2014-08-19 12:04 ` fd type from number Greg Freemyer
-- strict thread matches above, loose matches on Subject: below --
2014-08-19 15:38 Loris Degioanni
2014-08-19 15:54 ` Daniel Baluta
2014-08-19 16:02 ` Valdis.Kletnieks at vt.edu
2014-08-19 16:34 ` Loris Degioanni
2014-08-20 9:33 ` Rohan Puri
2014-08-22 19:03 ` Loris Degioanni
2014-08-23 5:26 ` Rohan Puri
2014-08-19 16:10 ` Greg KH
2014-08-19 16:36 ` Loris Degioanni
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=53F29E58.5060202@draios.com \
--to=loris@draios.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).