Task: Thread Synchronization

You will find a multi-threaded program in the upstream repository without any synchronization. Your task is to add correct and proper synchronization to make the program run flawlessly.
If you don’t know where and how to start, look at the help section below. While implementing, make sure to read the comments found in the assignment code, and if anything is unclear, come back to this Wiki.

Main Idea

This time, we provide a framework for Airport Check-In. The central roles in this scenario are:

Passengers – aim to check in either by using the self-check-in service or the traditional check-in desk.
Employees – work at the check-in desks, assisting passengers with the process.
Self-check-in kiosks – automated machines that passengers interact with for self-check-in.
Maintainers – responsible for servicing the self-check-in machines, which occasionally go out of service.

The passenger decides which check-in method to use. The workflow then branches as follows:

Traditional Check-In:

The check-in lane is considered open once the first employee arrives and opens it. Before this, passengers for the flight should not queue.
Employees are responsible for processing check-ins and will only work (attempt to check-in) if there is a passenger in the queue.
Once the check-in process is complete, the employee notifies the passenger, who may proceed to the gate.
Ensure your synchronization method properly releases employees when there are no more passengers waiting.

Self Check-In:

Self-check-in machines are available at all times; they do not have specific opening hours.
When a passenger arrives and selects an available machine, the interaction begins.
The machine starts in the READY state. Once the passenger selects the machine, it transitions to the START state.
The machine then transitions to the ID_SCAN state, allowing the passenger to scan their ID or boarding pass.
After a successful scan, the machine moves to the PASSENGER_IDENTIFIED state, printing the ticket.
Once the ticket is printed, the passenger can proceed to the express line for baggage drop-off or head directly to the gate.
After completing the check-in process, the machine either returns to the READY state or enters OUT_OF_SERVICE if it requires maintenance.
Maintainers work in their own rythums, checking self-check-in kiosks. If a machine goes out of service, they repair it and make it available for further use.

Ensure that the provided comments and hints in the code are followed, and achieve the described workflow using only synchronization primitives.

Task

Identify all actors and resources in the programs.
You need to ensure that the resources are acquired safely.
Think about potential data races and deadlock scenarios.
Use synchronization primitives correctly to make access to all shared resources thread-safe.
All shared resources must be accessed by only one thread at a time!
As with all other assignments, you can still lose points during the interviews if you cannot explain your solution satisfactorily or any cheating is detected.
The individual tasks are built to encourage the usage of at least one mutex, one semaphore, and one condition variable. Strongly think about which locking principles make the most sense in which situations.
Notice the marked TODO fields and which files are not to be modified.
Make sure to read the code as well as the function headers carefully.

Test your programs multiple times and with numerous parameters to find possible threading errors. Threading errors tend to crash programs/produce incorrect output very irregularly and are sometimes hard to reproduce.
Follow the “divide and conquer” principle and take a modular approach to the implementation. Start by implementing the traditional check-in first, then move on to self-check-in without maintenance and baggage drop, gradually adding more options as needed.
Make use of testing_defines.h – this allows you to easily activate, deactivate, or randomize self-check-in, baggage drop, and maintenance features!

Building

This assignment uses CMake as a build system. The essential build steps are as follows:

in-source building:

cd A2/
cmake .
make

out-of-source building:

cd A2/
mkdir build && cd build
cmake ..
make

Notice that an executable titled restaurant has been created in the folder you called make in. You can now start the program by executing the command ./airport num_passengers num_emoloyees num_selfcheckins, e.g. ./airport 1 1 1.

Common problems

This task is about locking. Do not wrap your head around different edge cases. Only make sure every shared resource is correctly locked.
Avoid potential deadlocks! Locks have to be locked in the same order.
Do not unlock a mutex multiple times, do not destroy a locked mutex, and especially do not unlock a mutex from a thread not owning it. Consider scenarios that lead to undefined behavior! (check out the man page)
You don’t have to change the cancellation state and/or type of any thread!
Use assert statements to check the return values of the pthread_* and sem_* functions to catch erroneous usage!

General notes

You are responsible only for locking. Do not change the program logic (except an if/while loop directly related to a synchronization primitive)!
==> Do not observe the codebase as an optimization or improvement opportunity. Instead, consider it a runway where you must make everything work correctly using only the learned synchronization primitives.
No new non-synchronization variables, code modifications, or reorganizations are allowed.
Timeout is a good sign for deadlock, lost signals, or overlocking. Make sure you don’t introduce any of these problems in your program.
You have a free choice of synchronization primitives. We don’t restrict you anywise, but only encourage you to use all those mentioned in the lecture as the goal of this task is to get familiar with them.
Ideally do not push any custom debug messages!
Make sure printf messages indicating an unlogical program flow do not get printed! (e.g. “[OOPS] Passenger xy appears to be early for their check-in!…“).
Ensure that the message “[ OK ] !! B O N V O Y A G E !!’ is the very last that appears in stdout!

Help

The spirit of this course is that you should learn to look up technical concepts and implement practical tasks by yourself. However, here is some help in case you get lost:

Most important resource: Manual pages for the pthreads (POSIXthreads) functions

man pthreads
man pthread_mutex_lock
man pthread_cond_wait
man < ... >

If you need a rough overview of the pthread library and how to lock correctly, make sure to check out the pthread tutorial (PDF) by Peter C. Chapin. It contains a lot of information you might need for the first and second assignments.

Note: If you get an error while trying to open the manual pages for pthread_mutex_lock, you can install the glibc-doc (sudo apt-get install glibc-doc) package to fix the issue.

Some important concepts

Always look up the function you use in their man pages. They will tell you how each function behaves in much more detail.

Semaphore Holds an integer value that can be increased and decreased by threads.
- A fixed amount of threads can enter.
- It puts the calling thread to sleep when it wants to decrease the value and has reached 0 or less.
- Sleeping threads are woken up when another thread increases the value.
- Datatype: sem_t
- Popular functions: sem_init, sem_destroy, sem_wait, sem_post
- See also https://linux.die.net/man/7/sem_overview

Mutex Primitive that can be used to make sure only one thread accesses critical sections of code simultaneously.
- Only one thread can enter.
- It can be locked and unlocked.
- If a thread tries to lock an already locked mutex, it is put to sleep until the mutex is unlocked by the thread that currently has it locked.
- A mutex applies the same concept as a semaphore with the values 0 or 1.
- Datatype: pthread_mutex_t
- Popular functions: pthread_mutex_init, pthread_mutex_destroy, pthread_mutex_lock, pthread_mutex_unlock
- See also https://hpc-tutorials.llnl.gov/posix/

Condition Variable Primitive that can be used to put threads to sleep and wake them up from other threads.
- A CV is ideal for many cases where one thread needs to wait for the result of some processing in another thread.
- They are always protected by an accompanying mutex.
- Datatype: pthread_cond_t
- Popular functions: pthread_cond_init, pthread_cond_destroy, pthread_cond_wait, pthread_cond_signal, pthread_cond_broadcast
- See also https://hpc-tutorials.llnl.gov/posix/

Assignment Tutor

If you have any questions regarding this assignment, go to Discord and read through the SLP channels. The probability that your question was already answered or some discussions will lead you in the right direction is quite high. If not so, just ask in the corresponding channel.

If you have a more direct question regarding your specific solution, you can also ask the tutor who organizes this assignment:

Nedžma Mušović, nedzma.musovic@student.tugraz.at