Menene race conditions, kuma yaya mutexes da semaphores ke hana su?

Question

IT Interview Practice · Accepted Answer

Idan threads da yawa suka raba bayanai, ayyukansu na iya haɗuwa (interleave) a tsakiyar sabuntawa mai matakai da yawa, suna haifar da race condition — bug inda sakamako ya dogara da lokaci mara tsinkaya. Synchronization shi ne saitin kayan aiki da ke tilasta tsari mai aminci.

Matsalar: race condition

count++ yana kama da atomic amma da gaske read-modify-write ne:

## Matsalar: race condition

`count++` yana kama da atomic amma da gaske read-modify-write ne:

```c
// two threads, shared int count = 0, each does count++ once
// thread A: read count (0) ─┐           interleaving loses an update:
// thread B: read count (0) ─┤  both read 0, both write 1 → count == 1, not 2
// thread A: write 1         │
// thread B: write 1         ┘
```

Tazarar da ke tsakanin karatu da rubutu ita ce **critical section** — code da ke taɓa shared state kuma bai kamata ya gudana lokaci guda ba.

## Kayan aikin

- **Mutex (lock)** — keɓancewar juna (mutual exclusion): thread ɗaya kaɗai ke riƙe shi a lokaci guda; sauran suna toshewa har sai an sake shi. Naɗe critical section:

```c
pthread_mutex_lock(&m);
count++;                 // critical section — exclusive
pthread_mutex_unlock(&m);
```

- **Semaphore** — counter da ke ba da damar har *N* masu riƙe lokaci guda. Binary semaphore (N=1) yana aiki kamar lock; counting semaphore yana iyakance, misali, connection pool a N masu amfani. Ana kuma amfani da shi don **signaling** tsakanin threads (producer/consumer).
- **Condition variable** — yana bar thread ya yi barci har sai wani sharaɗi ya zama gaskiya (misali "queue ba fanko ba"), yana farkawa ba tare da busy-waiting ba.
- **Atomic operations** — umarnin hardware kamar compare-and-swap (CAS) da ke yin read-modify-write ba tare da rabuwa ba, suna ba da damar lock-free counters.

## Tarko

Locks suna magance races amma suna kawo sabbin haɗura: **deadlock** (threads suna jiran locks na juna), **priority inversion**, da **contention** (threads suna zama jere, suna kashe parallelism). Ƙa'idar gama-gari: ka riƙe critical sections **gajere**, kuma kullum ka karɓi locks da dama a cikin **tsari na duniya mai daidaito**.

## Me ya sa yake da muhimmanci

Bugs na concurrency na cikin mafi wahalar samu — ba su da tsinkaya kuma sau da yawa suna ɓacewa a ƙarƙashin debugger. Masu hira suna son ganin cewa za ka iya *hango* critical section, zaɓi madaidaicin primitive (mutex vs semaphore vs atomic), da tunani game da yanayin gazawa (deadlock, contention). Wannan yana shafar kai tsaye kowane server mai threads da yawa, shared cache, ko counter.

Matsalar: race condition

Kayan aikin

Tarko

Me ya sa yake da muhimmanci

Tambayoyi masu alaƙa