Nevermind!This is how it works if anybody wants to know:It reads the entries
from the previous buffer and sends another buffer to read the rest of the
entries. This happens repeatedly until all the entries are read :D
On Wednesday, 10 June, 2020, 9:48:45 pm IST, Shubham Bhagat
<dmarc-noreply@xxxxxxxxxxxxx> wrote:
Hello,While I've been working on my GSoC project, I've come across kernel
interface hooks whose behaviour isn't very clear to me. Any help would be
appreciated.
The hook: "read_dir"Link to hook details:
https://www.haiku-os.org/docs/api/structfs__vnode__ops.html#a482878bf7588145c42d16c012a3de2e8
This hook reads the directory entries into a buffer and the buffer size being
small will cause an error.What is the behaviour after this? Is the hook invoked
again with a larger buffer and previous reading of entries goes in vain? Or
does it read the entries from the previous buffer and send another buffer to
read the rest of the entries (This makes sense) ? Or is there some other kind
of behaviour?