| 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
| ||
|
Message-ID: <Pine.LNX.4.61.0701311943110.13737@yvahk01.tjqt.qr> Date: Wed, 31 Jan 2007 19:45:02 +0100 (MET) From: Jan Engelhardt <jengelh@...ux01.gwdg.de> To: Helge Hafting <helge.hafting@...el.hist.no> cc: Eddie Pettis <pettis.eddie@...il.com>, linux-kernel@...r.kernel.org Subject: Re: How to locate struct file * from a bio? On Jan 31 2007 16:18, Helge Hafting wrote: > Eddie Pettis wrote: >> Longer version: I am working on a project that requires measuring the >> popularity of each file in a filesystem. I have made several attempts >> to locate all the file reads by grepping for ->readpage() and >> ->readpages() calls, but I am still missing several file reads. I >> have not yet looked for file writes. > > 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. And to add the sugar on top: in case you can live without tracing / (root filesystem), you can write your very own fuse filesystem layer in a few minutes and trace every small thing. Or perhaps take an existing project (aufs/unionfs) and enhance the module with some the wanted hooks, etc. Jan -- - 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/
Powered by blists - more mailing lists