<div dir="ltr"><div>Greetings</div><div><br></div>Didn't they remove {read,write}_proc_t in linux-3.10? You may have to provide full file_operations for a proc file.<div><div><br></div><div>Best Regards</div><div>-Emil</div>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jul 21, 2013 at 11:55 AM, Hua Siyuan <span dir="ltr"><<a href="mailto:jonnyhsy@foxmail.com" target="_blank">jonnyhsy@foxmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi All,<div><br></div><div>I'm now studying proc file system. I now know that read_proc_t function is called when the proofs file is read, and so for write_proc_t function when the proofs file is written to. But I also find the file_operaitons* field in the definition of proc_dir_entry, and this example code (<a href="http://linux.die.net/lkmpg/x810.html" target="_blank">http://linux.die.net/lkmpg/x810.html</a>). </div>
<div><br></div><div>So I'm confused that what happened if I provide both read_proc_t function, and the read function in file_operations structure? Thanks very much.</div><div><br></div><div>Best,</div><div>Siyuan</div>
</div><br>_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
<br></blockquote></div><br></div>