:
: > Why not just track the opens independantly in the overloading code?
:
:I'm not sure I know what you mean. I don't just need to track
:multiple open/closes, I need to be able to hang a pointer off of
:something that I can get at durning an mmap() or ioctl() syscall so
:that I can tell wh
Matt Dillon writes:
> :To handle the multiple open problem, I'm overloading the open and
> :close system calls. Upon open, I call the native open, then I grovel
> :around in the process' open file table looking for my special file.
> :When I find it, I mark fp->f_nextread with a magic number
:To handle the multiple open problem, I'm overloading the open and
:close system calls. Upon open, I call the native open, then I grovel
:around in the process' open file table looking for my special file.
:When I find it, I mark fp->f_nextread with a magic number, then store
:a pointer to the pe
