Skip to content

Mutex requirements#146

Merged
parphane merged 2 commits into
zephyrproject-rtos:mainfrom
nashif:topic/mutex/fixes_001
Jul 23, 2026
Merged

Mutex requirements#146
parphane merged 2 commits into
zephyrproject-rtos:mainfrom
nashif:topic/mutex/fixes_001

Conversation

@nashif

@nashif nashif commented Jun 25, 2026

Copy link
Copy Markdown
Member
  • requirements: correct Mutex umbrella requirement
  • requirements: add missing Mutex software requirements

nashif added 2 commits June 25, 2026 19:05
The single existing Mutex requirement (ZEP-SRS-6-1) was vague, embedded a
parenthetical note in its statement, and had no parent link. Reword it to
state the mutex's mutual-exclusion purpose, clean up the user story
wording, and link it to the Mutex system requirement (ZEP-SYRS-13).

The detailed mutex behavior (locking, unlocking, ownership, recursion,
priority inheritance) is added in a separate change.

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
The Mutex document previously contained only a single high-level
requirement. Add eleven requirements (ZEP-SRS-6-2 .. ZEP-SRS-6-12)
covering the implemented k_mutex behavior: definition (compile time, run
time), locking (acquiring an unowned mutex, blocking on a mutex owned by
another thread, lock timeout and timeout expiry), recursive locking by
the owner, unlocking (by the owner and the error for a non-owner), and
priority inheritance.

The requirements reflect the currently implemented k_mutex API behavior
following the Route 3s approach and link to the Mutex system parent
(ZEP-SYRS-13). UIDs were generated with "strictdoc manage auto-uid".

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
@parphane parphane mentioned this pull request Jun 30, 2026
3 tasks

@parphane parphane left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Performed review:

  1. Agreed with change on "Mutex Kernel Object", this SW req is about Mutex. If we want a generic requirement, we should make one at system level.
  2. Properly traced to sys req ZEP-SYRS-13
  3. 4 functions covered by requirements, internal function logic defined without ambiguity
  4. No checklist violation https://docs.zephyrproject.org/latest/safety/safety_requirements/safety_requirements_checklist.html

@parphane
parphane merged commit 799eab0 into zephyrproject-rtos:main Jul 23, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants