Databases
StackOverflow2013
Postsdbo
POUnderstanding loff_t *offp for file_operations
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnderstanding loff_t *offp for file_operations
    primarykey
    data
    text
    <p>I'm designing a device driver that simply reads and writes to a character buffer. My question is however regarding the two functions in the <code>file_operations</code> structure <code>read</code> and <code>write</code>. I don't truly understand what <code>loff_t *offp</code> really is. I know that for both the read and write operations that <code>*offp</code> is the file offset meaning the current reading/writing position of the file, however I'm not even sure what it means to write or read to/from a device file.</p> <p>From what I gathered, and this is how I am writing and reading from my device is that I create a structure which represents my device which I call <code>my_char_struct</code> which is shown bellow.</p> <pre><code>struct my_char_structure{ struct cdev my_cdev; struct semaphore sem; char *data; ssize_t data_size; unsigned int access_key; unsigned long size; }; </code></pre> <p>This is a static structure that is initialized and pointed to when my driver is <code>insmod</code> as such. </p> <pre><code>static dev_t dev_num; static struct my_char_structure Dev; int start_mod(void){ //Because we are dealing with a fictitious device, I want //the driver to create my two devices with arbitrarily //assigned major numbers. struct my_char_structure *my_dev = &amp;Dev; int err; alloc_chrdev_region(&amp;dev_num, FIRST_MINOR, COUNT, DEVICE_NAME); sema_init(&amp;(my_dev-&gt;sem),1); cdev_init(&amp;(my_dev-&gt;my_cdev), &amp;fops); my_dev-&gt;my_cdev.owner = THIS_MODULE; my_dev-&gt;my_cdev.ops = &amp;fops;// fops is my file operations struct err = cdev_add(&amp;my_dev-&gt;my_cdev, dev_num, COUNT); if(err&lt;0) printk(KERN_ALERT "There was an error %d.",err); printk(KERN_ALERT " insmod to major number %d",MAJOR(dev_num)); return 0; } module_init(start_mod); </code></pre> <p>When my device is open, I just make a pointer for the file open to point to that static structure that I've set up during <code>module_init(start_mod)</code> as such ...</p> <pre><code>int dev_open(struct inode *in_node, struct file *filp){ static struct my_char_structure *my_dev; my_dev = container_of(in_node-&gt;i_cdev, struct my_char_structure, my_cdev); printk(KERN_ALERT "The device number is %d",iminor(in_node)); if(!my_dev) printk(KERN_ALERT "something didn't work. my_dev not initialized."); filp-&gt;private_data = my_dev; return 0; } </code></pre> <p>What my read and write methods do is modify that initial structure Dev, that I've pointed to with my open files. Whatever I <code>copy_to_user</code> from my structure is what the user considers been written to the device and whatever I <code>copy_from_user</code> the user thinks they're writing. But beyond changing my initial structure Dev, the idea of file position or offset doesn't make sense unless it refers to a pointer to buffered memory within the kernel for some arbitrary structure or type. Thats the only interpretation that I have for the file offset ... is this correct? Is that what the <code>loff_t *offp</code> here refers to?</p> <pre><code>write(struct file *filp, const char __user *buff, size_t count, loff_t *offp) read(struct file *filp, char __user *buff, size_t count, loff_t *offp) </code></pre> <p>(given my understanding is correct) When some file_operation such as read/write is called and I hadn't set <code>*offp</code> personally, what is loff_t *offp initially set to? </p> <p>If in the last file_operation offp = some_arbitrary_address(because I told it so), is that what the offp would be set to when this operation is called again? </p> <p>What happens if I have other file_opens operations running, will it set to what the last file_operation left it as, or will it keep a tab of which file_open operation it used and replace *offp to what the file_open had it at? </p> <p>The concept of a char device is too abstract for me when it seems that the device itself doesn't even store the information like a file should, but rather its the driver that saves the information. I hope I've explained my fogginess and I'll clear up anything that I seem ambiguous about.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDr.Knowitall
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUnderstanding loff_t *offp for file_operations
      1. USDr.Knowitall
      1. VTFavorite
    2. VO
      singulars
      1. POUnderstanding loff_t *offp for file_operations
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUnderstanding loff_t *offp for file_operations
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload