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: <20241211174029.GC6698@frogsfrogsfrogs>
Date: Wed, 11 Dec 2024 09:40:29 -0800
From: "Darrick J. Wong" <djwong@...nel.org>
To: Bingwu Zhang <xtex@...s.net>
Cc: Jonathan Corbet <corbet@....net>, Miklos Szeredi <miklos@...redi.hu>,
	Bingwu Zhang <xtex@...c.io>, linux-fsdevel@...r.kernel.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-unionfs@...r.kernel.org, linux-xfs@...r.kernel.org,
	~xtex/staging@...ts.sr.ht
Subject: Re: [PATCH] Documentation: filesystems: fix two misspells

On Sun, Dec 08, 2024 at 11:54:47AM +0800, Bingwu Zhang wrote:
> From: Bingwu Zhang <xtex@...c.io>
> 
> This fixes two small misspells in the filesystems documentation.
> 
> Signed-off-by: Bingwu Zhang <xtex@...c.io>

Yep, typoes happun, thanks for the patch.
Reviewed-by: "Darrick J. Wong" <djwong@...nel.org>

--D

> ---
> I found these typos when learning about OverlayFS recently.
> ---
>  Documentation/filesystems/iomap/operations.rst | 2 +-
>  Documentation/filesystems/overlayfs.rst        | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/filesystems/iomap/operations.rst b/Documentation/filesystems/iomap/operations.rst
> index ef082e5a4e0c..2c7f5df9d8b0 100644
> --- a/Documentation/filesystems/iomap/operations.rst
> +++ b/Documentation/filesystems/iomap/operations.rst
> @@ -104,7 +104,7 @@ iomap calls these functions:
>  
>      For the pagecache, races can happen if writeback doesn't take
>      ``i_rwsem`` or ``invalidate_lock`` and updates mapping information.
> -    Races can also happen if the filesytem allows concurrent writes.
> +    Races can also happen if the filesystem allows concurrent writes.
>      For such files, the mapping *must* be revalidated after the folio
>      lock has been taken so that iomap can manage the folio correctly.
>  
> diff --git a/Documentation/filesystems/overlayfs.rst b/Documentation/filesystems/overlayfs.rst
> index 4c8387e1c880..d2a277e3976e 100644
> --- a/Documentation/filesystems/overlayfs.rst
> +++ b/Documentation/filesystems/overlayfs.rst
> @@ -156,7 +156,7 @@ A directory is made opaque by setting the xattr "trusted.overlay.opaque"
>  to "y".  Where the upper filesystem contains an opaque directory, any
>  directory in the lower filesystem with the same name is ignored.
>  
> -An opaque directory should not conntain any whiteouts, because they do not
> +An opaque directory should not contain any whiteouts, because they do not
>  serve any purpose.  A merge directory containing regular files with the xattr
>  "trusted.overlay.whiteout", should be additionally marked by setting the xattr
>  "trusted.overlay.opaque" to "x" on the merge directory itself.
> 
> base-commit: 7503345ac5f5e82fd9a36d6e6b447c016376403a
> -- 
> 2.47.1
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ