Code Flow of read() system call

[GoogleCodeExporter]

1. Summary/requirements from the document :

The document should explain the code flow of the read() system call. The 
document should explain the whole code flow from user-space to kernel space to 
hardware.

2. Required For (explain the need of the document) :

The document is required to understand the places in the file system's code 
where we can place our hooks.

3. Reference :

UTLK and LKD

4. Flags :

a. Need Diagrams (Y/N)              : Y

b. Need Flowcharts (Y/N)            : Y

c. Publish PDF document (Y/N)       : Y

Original issue reported on code.google.com by binarywarriors5@gmail.com on 25 Sep 2010 at 8:28

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The pdf includes the flowchart of read system call from user space to kernel 
space to hardware

Original comment by binarywarriors5@gmail.com on 4 Oct 2010 at 5:47

• Changed state: Finishing

Attachments:

• read_sys_call.pdf

[GoogleCodeExporter]

The flow chart looks fine but the document was expected to contain the 
explanation of of the relevant functions.

I want you all to find the entry point of the read() to the ext2 module. When 
and with what parameters the read system call enters the ext2 module's code.

We have to place hooks in the ext2 module accordingly.

Original comment by binarywarriors5@gmail.com on 5 Oct 2010 at 5:52

• Changed state: Working

[GoogleCodeExporter]

Original comment by kashish....@gmail.com on 13 Mar 2011 at 6:23

• Changed state: Finishing

[GoogleCodeExporter]

Explanation with source code is appreciable
-Nakul

Original comment by NakulGIy...@gmail.com on 3 Nov 2011 at 5:51