While reading device drivers by rubini, i found following statement related to loff_t fops.
The current reading or writing position. loff_t is a 64-bit value (long long in gcc terminology). The driver can read this value if it needs to know the current position in the file, but should never change it (read and write should update a position using the pointer they receive as the last argument instead of acting on filp->f_pos directly).
so why can't we update the position directly by using filp->f_pos structure.
Thanks in advance,
Deepak Joshi.
Try the all-new Yahoo! Mail . "The New Version is radically easier to use" ? The Wall Street Journal
