From: loris@draios.com (Loris Degioanni)
To: kernelnewbies@lists.kernelnewbies.org
Subject: fd type from number
Date: Tue, 19 Aug 2014 09:36:25 -0700 [thread overview]
Message-ID: <53F37D09.80307@draios.com> (raw)
In-Reply-To: <20140819161051.GA31971@kroah.com>
On 8/19/2014 9:10 AM, Greg KH wrote:
> On Tue, Aug 19, 2014 at 08:38:24AM -0700, Loris Degioanni wrote:
>> (resending making sure this is not part of another thread)
>>
>> I'm looking for an efficient way to determine the type of an fd (file,
>> socket...) given its number, from a kernel module.
> You don't have a "number" from within the kernel, you have a pointer to
> the full file descriptor structure, right? If so, what is missing from
> that structure that you can not find?
I do have the FD number, because it's coming from intercepting a system
call.
>
>> 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?
> What exactly are you trying to do with this? And what does it matter
> what "type" of thing a file descriptor is? What can you do with that
> information?
I just sent another email with some explanation.
Loris
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2014-08-19 16:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 15:38 fd type from number 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-18 16:25 TCP/UDP 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 ` fd type from number Loris Degioanni
2014-08-19 12:04 ` Greg Freemyer
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=53F37D09.80307@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).