linux-kernel - Re: get device from file struct

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0612131200430.25870@yvahk01.tjqt.qr>
Date:	Wed, 13 Dec 2006 12:03:18 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Silviu Craciunas <silviu.craciunas@....ac.at>
cc:	linux-kernel@...r.kernel.org
Subject: Re: get device from file struct


>> >thanks for the reply, the block device can be determined with the major
>> >and minor numbers , what I would be more interested in is if one can get
>> >the net_device struct from the file struct
>> 
>> Just how are you supposed to match files and network devices?
>> 
>
>from the struct file you can get the struct socket and from there to the
>struct sock .

That only applies when using PF_LOCAL sockets.

>What I would like to find out is where the data is coming
>from (read) and where it is going to(write) or if it is even possible to
>find the net device out using the struct file.

I really don't get what you want.

Suppose a daemon reads from a socket (PF_INET), then there is a file descriptor
to sockfs (look into /proc/$$/fd/). Well, then you may be able to get the
struct file for that socket, but it does not connect to a regular file
(S_IFREG) at all.


	-`J'
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/