Re: Kernel module that catches a syscall (i/o event)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2007-02-24 at 20:33 +0000, Liran wrote:
> Hey everyone,
> 
> Hopefully, this is not off-topic for this mailing list.
> 
> I want to develop a kernel module that will be used to account for the
> input/output of files on the system
> and was wondering about doing it by intercepting the open() / read() / write()
> system calls with their size attributes
> and using that as a counter. (Later on, I wish to attach to a specific pid or
> account for all i/o for a specific user but that's later).


> So here comes my question - how do I go about doing that? Should I go with the
> intercepting thing or are
> there more elegant ways?

I think your first misconception is that all IO starts with a syscall...
that's actually very much not the case (hint: mmap'd areas). So the very
first assumption of what you are trying to do is already not valid ...
maybe time to rethink?


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org


--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux