linux-kernel - Re: [PATCH] overlayfs.rst: Fix and improve grammar

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOQ4uxjESOJsb2GDx-c==_cLtF=wqtDAprcDmjwiq25hyzQFwA@mail.gmail.com>
Date: Tue, 7 Jan 2025 12:13:25 +0100
From: Amir Goldstein <amir73il@...il.com>
To: Geert Uytterhoeven <geert+renesas@...der.be>, Jonathan Corbet <corbet@....net>
Cc: Miklos Szeredi <miklos@...redi.hu>, linux-unionfs@...r.kernel.org, 
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] overlayfs.rst: Fix and improve grammar

On Tue, Jan 7, 2025 at 9:45 AM Geert Uytterhoeven
<geert+renesas@...der.be> wrote:
>
>   - Correct "in a way the" to "in a way that",
>   - Add a comma to improve readability.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>

Acked-by: Amir Goldstein <amir73il@...il.com>

John,

Please take this patch via the documentation tree,
as I have no overlayfs patches queued for v6.14.

Thanks,
Amir.

> ---
>  Documentation/filesystems/overlayfs.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/filesystems/overlayfs.rst b/Documentation/filesystems/overlayfs.rst
> index 4c8387e1c88068fa..a93dddeae199491a 100644
> --- a/Documentation/filesystems/overlayfs.rst
> +++ b/Documentation/filesystems/overlayfs.rst
> @@ -266,7 +266,7 @@ Non-directories
>  Objects that are not directories (files, symlinks, device-special
>  files etc.) are presented either from the upper or lower filesystem as
>  appropriate.  When a file in the lower filesystem is accessed in a way
> -the requires write-access, such as opening for write access, changing
> +that requires write-access, such as opening for write access, changing
>  some metadata etc., the file is first copied from the lower filesystem
>  to the upper filesystem (copy_up).  Note that creating a hard-link
>  also requires copy_up, though of course creation of a symlink does
> @@ -549,8 +549,8 @@ Nesting overlayfs mounts
>
>  It is possible to use a lower directory that is stored on an overlayfs
>  mount. For regular files this does not need any special care. However, files
> -that have overlayfs attributes, such as whiteouts or "overlay.*" xattrs will be
> -interpreted by the underlying overlayfs mount and stripped out. In order to
> +that have overlayfs attributes, such as whiteouts or "overlay.*" xattrs, will
> +be interpreted by the underlying overlayfs mount and stripped out. In order to
>  allow the second overlayfs mount to see the attributes they must be escaped.
>
>  Overlayfs specific xattrs are escaped by using a special prefix of
> --
> 2.43.0
>
>