From 9e0168b018c4548eedd190f7ca760431f040a736 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Mon, 30 Mar 2020 21:41:47 +0200 Subject: [PATCH] openat2.2: Minor tweaks to RESOLVE_IN_ROOT text Signed-off-by: Michael Kerrisk --- man2/openat2.2 | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/man2/openat2.2 b/man2/openat2.2 index d29f6020e..f6f69669a 100644 --- a/man2/openat2.2 +++ b/man2/openat2.2 @@ -275,7 +275,7 @@ the caller should explicitly specify .BR RESOLVE_NO_MAGICLINKS . .TP .B RESOLVE_IN_ROOT -Treat +Treat the directory referred to by .I dirfd as the root directory while resolving .IR pathname . @@ -295,8 +295,7 @@ However, unlike .BR chroot (2) (which changes the filesystem root permanently for a process), .B RESOLVE_IN_ROOT -allows a program to efficiently restrict path resolution for selected -open operations. +allows a program to efficiently restrict path resolution on a per-open basis. .\" FIXME The next piece is unclear (to me). What kind of ".." escape .\" attempts does chroot() not detecct that RESOLVE_IN_ROOT does? The