linux-kernel - Re: How to locate struct file * from a bio?

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 31 Jan 2007 13:55:15 -0500
From:	"Eddie Pettis" <pettis.eddie@...il.com>
To:	"Helge Hafting" <helge.hafting@...el.hist.no>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How to locate struct file * from a bio?

On 1/31/07, Helge Hafting <helge.hafting@...el.hist.no> wrote:
> Eddie Pettis wrote:
> > Short question:  Is it possible to locate the struct file * associated
> > with a bio?  If so, how?
> >
>
> Looks like you do this the wrong way.

Agreed.  It was a bad hack based on something I had done previously.

>
> Why don't you tap into "open" instead?
> Here you can note who opens the file and if they open it for
> reading or writing.  If you really need the amount of data
> transferred, consider trapping the read and write syscalls too.

I added hooks to the sys_* system calls for read/write/open/close from
userspace, and that seems to work.

Thanks!

>
> Helge Hafting
>
-
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/