lifubang 5560d55bfd libct/specconv: fix partial clear of atime mount flags ...

When parsing mount options into recAttrSet and recAttrClr,
the code sets attr_clr to individual atime flags (e.g.
MOUNT_ATTR_NOATIME or MOUNT_ATTR_STRICTATIME) when clearing
atime attributes. However, this violates the kernel's
requirement documented in mount_setattr(2)[1]:

> Note that, since the access-time values are an enumeration
> rather than bit values, a caller wanting to transition to a
> different access-time setting cannot simply specify the
> access-time setting in attr_set, but must also include
> MOUNT_ATTR__ATIME in the attr_clr field.  The kernel will
> verify that MOUNT_ATTR__ATIME isn't partially set in
> attr_clr (i.e., either all bits in the MOUNT_ATTR__ATIME
> bit field are either set or clear), and that attr_set
> doesn't have any access-time bits set if MOUNT_ATTR__ATIME
> isn't set in attr_clr.

Passing only a single atime flag (e.g. MOUNT_ATTR_RELATIME) in
attr_clr causes mount_setattr() to fail with EINVAL.

This change ensures that whenever an atime mode is updated,
attr_clr includes MOUNT_ATTR__ATIME to properly reset the
entire access-time attribute field before applying the new mode.

[1] https://man7.org/linux/man-pages/man2/mount_setattr.2.html

Signed-off-by: lifubang <lifubang@acmcoder.com>

2026-02-06 03:30:55 +00:00

..

cmd

fix(seccompagent): close received FDs, not loop index

2025-10-06 06:16:33 +08:00

fuzzing

remove broken fuzzer from oss-fuzz build script

2024-12-18 16:49:44 +00:00

integration

libct/specconv: fix partial clear of atime mount flags

2026-02-06 03:30:55 +00:00

rootless.sh

ci: ensure the cgroup(v1) parent always exists for rootless

2025-11-18 13:58:46 +00:00