System calls and their role in Operating Systems - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of a system call?

System calls allow user programs to:

A Directly access hardware devices without restrictions

B Request services from the operating system kernel

C Modify the source code of the operating system

D Run programs without using the CPU

💡 Hint

Think about how user programs interact with the operating system.

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

📋 Factual

intermediate

Which of the following is NOT typically a system call?

Identify the option that is generally not implemented as a system call in operating systems.

A Allocating memory dynamically within a program

B Opening a file

C Creating a new process

D Sending data over a network socket

💡 Hint

Consider which actions require kernel intervention versus those handled by the program itself.

Dynamic memory allocation (like malloc in C) is usually handled by the program's runtime library, not directly by system calls.

🔍 Analysis

advanced

Why do system calls involve a context switch between user mode and kernel mode?

Explain the reason behind switching modes during a system call.

A To allow the CPU to run multiple programs simultaneously

B To speed up the execution of user programs

C To protect the system by controlling access to hardware and resources

D To enable direct hardware manipulation by user programs

💡 Hint

Think about security and stability in operating systems.

The switch to kernel mode ensures that only trusted code can perform sensitive operations, protecting the system from accidental or malicious damage.

❓ Comparison

advanced

Compare system calls and library functions in terms of their interaction with the operating system.

Which statement correctly describes the difference between system calls and library functions?

A Library functions may call system calls internally to perform OS-level tasks

B System calls do not require switching to kernel mode, but library functions do

C System calls are implemented in user space, while library functions run in kernel space

D Library functions always provide direct hardware access without OS involvement

💡 Hint

Consider how libraries use system calls to interact with the OS.

Library functions often provide convenient interfaces and internally invoke system calls to request OS services.

❓ Reasoning

expert

What would likely happen if user programs could perform system calls without switching to kernel mode?

Consider the consequences if system calls executed entirely in user mode.

A The system would be more secure because user programs control hardware directly

B System calls would run faster without any risks

C There would be no change in system behavior or security

D User programs could cause system crashes or security breaches easily

💡 Hint

Think about the role of kernel mode in protecting the system.

Allowing system calls in user mode would remove protections, letting programs access hardware and memory directly, risking crashes and security issues.

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