set_robust_list

Partial in Antinomie 0.7.0 · Syscall list

Synopsis

long set_robust_list(struct robust_list_head *head, size_t len);

Number (x86-64)	273
ABI	64
Kernel entry point	sys_set_robust_list

This is the raw kernel prototype from the pinned Linux 6.12.94 schema, not the libc wrapper.

Description

Registers the list of robust futexes the kernel must release if the thread dies.

Arguments

Name	Type	Meaning
head (arg0)	struct robust_list_head *	Pointer to a robust list head.
len (arg1)	size_t	Length in bytes.

Return value

On success: 0.

In an Antinomie trace the Return column and the ret filter field show the raw kernel return value. On failure that is the negative errno, for example -2 for ENOENT, not the -1 plus errno that the libc wrapper gives. syscall.errno holds the positive errno and syscall.success is false.

Common errors

Raw return	Name	Meaning
-22	EINVAL	An argument is invalid.

Man page

set_robust_list(2) on man7.org

Captured by Antinomie

Coverage mark: Partial. The list head is recorded, but the kernel walks the list when the thread exits, so that traversal is recorded with the “not observed asynchronously” status.

Every call is recorded as an Entry record (the six argument words and the pointees copied at entry) and an Exit record (the return value and the pointees copied at exit).

Arguments

Argument	When	How	Recorded field key	Condition
head (arg0)	Entry	the pointer itself, as a raw word	args.0, args.raw[0]
↳ pointee	Entry	structure robust_list_head (24 bytes) as the program wrote it; “invalid extent” with no copy if len is not 24	arg0.head	always
↳ pointee	Entry	same 24 bytes, status “not observed asynchronously”	arg0.head.traversal	len is 24
len (arg1)	Entry	raw scalar word	args.1, args.len

Filter fields

• Result: ret, syscall.errno, syscall.success, syscall.duration_ns.
• Argument words: args.head (arg0), args.len (arg1); args.0 to args.5 by position.
• Structure robust_list_head behind head (arg0): args.head.<member> for futex_offset, list.next, list_op_pending.

See Syscall Trace filter for the full syntax.

Known gaps

• The kernel stores only the pointer and walks the list when the thread exits.
• See the coverage mark above for the code paths that record a gap.

For what the capture statuses mean, see Capture statuses. For what is never recorded, see Known gaps.