public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Essien <champbreed1@gmail.com>
To: alx@kernel.org
Cc: linux-man@vger.kernel.org, Simon Essien <champbreed1@gmail.com>
Subject: [PATCH 2/2] path_resolution.7: document read-only mounts, ACLs, and immutable files
Date: Tue,  6 Jan 2026 11:26:27 +0000	[thread overview]
Message-ID: <20260106112627.83127-2-champbreed1@gmail.com> (raw)
In-Reply-To: <20260106112627.83127-1-champbreed1@gmail.com>

Address several FIXMEs by adding brief mentions of:
- EROFS errors on read-only filesystems.
- Access restrictions from filesystem ACLs.
- Access restrictions from immutable file attributes.

Signed-off-by: Simon Essien <champbreed1@gmail.com>
---
 man/man7/path_resolution.7 | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

diff --git a/man/man7/path_resolution.7 b/man/man7/path_resolution.7
index cdf21e1f7..78573f3c2 100644
--- a/man/man7/path_resolution.7
+++ b/man/man7/path_resolution.7
@@ -225,7 +225,12 @@ Similarly, Linux uses the fsgid ("filesystem group ID")
 instead of the effective group ID.
 See
 .BR setfsgid (2).
-.\" FIXME . say something about filesystem mounted read-only ?
+.P
+Even if a process has the necessary permissions to access or
+modify a file, an attempt to modify any part of the filesystem
+will fail with the error
+.B EROFS
+if the filesystem is currently mounted read-only.
 .SS Bypassing permission checks: superuser and capabilities
 On a traditional UNIX system, the superuser
 .RI ( root ,
@@ -256,8 +261,15 @@ The
 .B CAP_DAC_READ_SEARCH
 capability grants read and search permission
 on directories, and read permission on ordinary files.
-.\" FIXME . say something about immutable files
-.\" FIXME . say something about ACLs
+.P
+Beyond the standard permissions, access may also be restricted by
+filesystem-specific ACLs (Access Control Lists) or by
+immutable file attributes.
+See
+.BR acl (5)
+and
+.BR chattr (1)
+for more details.
 .SH SEE ALSO
 .BR readlink (2),
 .BR capabilities (7),
-- 
2.51.0


      reply	other threads:[~2026-01-06 11:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 11:26 [PATCH 1/2] man2: update glibc wrapper status and clean up FIXMEs Simon Essien
2026-01-06 11:26 ` Simon Essien [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260106112627.83127-2-champbreed1@gmail.com \
    --to=champbreed1@gmail.com \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox