System calls and their role in Operating Systems - Step-by-Step Execution

Concept Flow - System calls and their role

User Program Requests Service

↓

System Call Interface

↓

Operating System Kernel

↓

Perform Requested Operation

↓

Return Result to User Program

The user program asks the OS for a service via a system call, the OS performs it, then returns the result.

Execution Sample

Operating Systems

open("file.txt")
read(file_descriptor)
write(file_descriptor, data)
close(file_descriptor)

A program uses system calls to open, read, write, and close a file.

Analysis Table

Step	Action	System Call	Kernel Operation	Result Returned
1	Program requests to open file.txt	open("file.txt")	Locate file and prepare for access	File descriptor (e.g., 3)
2	Program requests to read from file	read(3)	Read data from file into buffer	Data read from file
3	Program requests to write data	write(3, data)	Write data to file	Number of bytes written
4	Program requests to close file	close(3)	Release file resources	Success confirmation
5	Program ends file operations	No further calls	No operation	End of system calls

💡 Program finishes file operations; no more system calls requested.

State Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
file_descriptor	None	3	3	3	None	None
buffer_data	Empty	Empty	Data read	Data read	Data read	Data read
write_status	None	None	None	Bytes written	Bytes written	Bytes written

Key Insights - 3 Insights

Why does the program need a file descriptor after opening a file?

The file descriptor is a simple number that the OS uses to track the open file. It is returned at Step 1 in the execution_table and used in later calls to identify which file to read, write, or close.

What happens if the program tries to read before opening a file?

Without a valid file descriptor from an open call, the read system call cannot work. This is shown by the need for Step 1 to succeed before Step 2 in the execution_table.

Why does the program need to close the file?

Closing the file releases resources held by the OS. Step 4 in the execution_table shows the close system call freeing these resources, preventing leaks or errors.

Visual Quiz - 3 Questions

Look at the execution_table, what is the file descriptor value returned after Step 1?

A 3

B None

C 0

D File name

💡 Hint

Check the 'Result Returned' column in Step 1 of the execution_table.

At which step does the program write data to the file?

A Step 2

B Step 4

C Step 3

D Step 1

💡 Hint

Look at the 'Action' and 'System Call' columns to find when write is called.

If the program skips closing the file, what variable in variable_tracker remains unchanged after Step 4?

A buffer_data

B file_descriptor

C write_status

D None

💡 Hint

Check how file_descriptor changes after Step 4 in variable_tracker.

Concept Snapshot

System calls let user programs ask the OS to do tasks like file access.
The program calls a system call (e.g., open, read, write, close).
The OS kernel performs the operation and returns results.
File descriptors identify open files.
Closing files frees OS resources.
System calls are the bridge between user programs and hardware.

Full Transcript

System calls are special requests from user programs to the operating system to perform tasks like opening or reading files. The program calls a system call interface, which passes the request to the OS kernel. The kernel performs the operation, such as locating a file or reading data, and returns a result like a file descriptor or data read. For example, a program opens a file, reads data, writes data, and then closes the file. Each step involves a system call. The file descriptor is a number used to track the open file. Closing the file releases resources. This process ensures safe and controlled access to hardware and system resources.

Practice

1. What is the main purpose of a system call in an operating system?

easy

A. To write code that runs only on specific hardware

B. To directly access hardware without OS intervention

C. To compile programs into machine code

D. To allow programs to request services from the operating system

Solution

1. Step 1: Understand what system calls do

   System calls provide a way for programs to ask the operating system to perform tasks on their behalf, such as reading files or managing processes.

2. Step 2: Compare options with this role

   Only To allow programs to request services from the operating system correctly describes this role. Other options describe unrelated actions like direct hardware access or compilation.

3. Final Answer:

   To allow programs to request services from the operating system -> Option D

4. Quick Check:

   System call = request OS service [OK]

Hint: System calls let programs ask OS for help [OK]

Common Mistakes:

• Thinking system calls bypass the OS
• Confusing system calls with compiling
• Assuming system calls are hardware instructions

2. Which of the following is the correct way a program typically uses a system call?

easy

A. By calling a special function provided by the operating system

B. By directly writing machine code instructions

C. By modifying the operating system kernel

D. By sending signals to hardware devices

Solution

1. Step 1: Identify how programs interact with system calls

   Programs use system calls by calling special functions (APIs) provided by the OS, which then perform the requested service.

2. Step 2: Eliminate incorrect options

   Direct machine code writing or kernel modification is not how normal programs use system calls. Sending signals to hardware is also not the typical method.

3. Final Answer:

   By calling a special function provided by the operating system -> Option A

4. Quick Check:

   System call usage = OS function call [OK]

Hint: System calls are accessed via OS functions, not direct code [OK]

Common Mistakes:

• Thinking programs write machine code for system calls
• Believing programs modify the OS kernel directly
• Confusing hardware signals with system calls

3. Consider this pseudocode using a system call to open a file:

fd = open_file("data.txt")
if fd == -1:
    print("Error opening file")
else:
    print("File opened successfully")

What will be printed if the file does not exist?

medium

A. No output

B. File opened successfully

C. Error opening file

D. System crash

Solution

1. Step 1: Understand the system call behavior

   The open_file system call returns a file descriptor if successful, or -1 if it fails (e.g., file not found).

2. Step 2: Follow the conditional logic

   If fd == -1, the program prints "Error opening file". Since the file does not exist, fd will be -1.

3. Final Answer:

   Error opening file -> Option C

4. Quick Check:

   File missing -> fd = -1 -> error message [OK]

Hint: Open returns -1 on failure, triggers error print [OK]

Common Mistakes:

• Assuming file opens successfully even if missing
• Expecting no output on failure
• Thinking system calls cause crashes on errors

4. A program tries to read from a file using this code snippet:

bytes_read = read_file(fd, buffer, 100)
if bytes_read == 0:
    print("End of file reached")
elif bytes_read < 0:
    print("Read error")
else:
    print(f"Read {bytes_read} bytes")

But it always prints "Read error" even when the file exists. What is the likely problem?

medium

A. The print statement syntax is incorrect

B. The file descriptor fd is invalid or not opened properly

C. The file is empty

D. The buffer size is too large

Solution

1. Step 1: Analyze the meaning of bytes_read < 0

   A negative return value from read_file indicates an error, often caused by an invalid file descriptor.

2. Step 2: Check other options for plausibility

   Buffer size being large or file empty would not cause a read error. Print syntax errors cause compile/runtime errors, not read errors.

3. Final Answer:

   The file descriptor fd is invalid or not opened properly -> Option B

4. Quick Check:

   Read error -> invalid fd [OK]

Hint: Negative read means invalid file descriptor [OK]

Common Mistakes:

• Blaming buffer size for read errors
• Assuming empty file causes read error
• Confusing print syntax with read errors

5. You want to write a program that creates a new file, writes data to it, and then closes it using system calls. Which sequence correctly represents these steps?

hard

A. Open file -> Write data -> Close file

B. Write data -> Open file -> Close file

C. Close file -> Open file -> Write data

D. Open file -> Close file -> Write data

Solution

1. Step 1: Understand the logical order of file operations

   You must first open the file to get a handle, then write data to it, and finally close it to save and release resources.

2. Step 2: Match the correct sequence

   Only Open file -> Write data -> Close file follows this logical order. Other options have steps in wrong order, which would cause errors or no effect.

3. Final Answer:

   Open file -> Write data -> Close file -> Option A

4. Quick Check:

   Open before write, close last [OK]

Hint: Always open before writing, close after done [OK]

Common Mistakes:

• Trying to write before opening file
• Closing file before writing
• Skipping the close step