From: Randy Dunlap <rdunlap@infradead.org>
To: Alperen Aksu <aksulperen@gmail.com>, corbet@lwn.net
Cc: linux-xfs@vger.kernel.org, linux-doc@vger.kernel.org,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] Documentation/filesystems/xfs: Fix typo error
Date: Thu, 21 Aug 2025 09:54:20 -0700 [thread overview]
Message-ID: <70c48801-83fe-413f-8a8e-5db71c8d1c8d@infradead.org> (raw)
In-Reply-To: <20250821131404.25461-1-aksulperen@gmail.com>
On 8/21/25 6:13 AM, Alperen Aksu wrote:
> Fixed typo error in referring to the section's headline
> Fixed to correct spelling of "mapping"
>
> Signed-off-by: Alperen Aksu <aksulperen@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Documentation/filesystems/xfs/xfs-online-fsck-design.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> index e231d127cd40..b39b588bb995 100644
> --- a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> +++ b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> @@ -475,7 +475,7 @@ operation, which may cause application failure or an unplanned filesystem
> shutdown.
>
> Inspiration for the secondary metadata repair strategy was drawn from section
> -2.4 of Srinivasan above, and sections 2 ("NSF: Inded Build Without Side-File")
> +2.4 of Srinivasan above, and sections 2 ("NSF: Index Build Without Side-File")
> and 3.1.1 ("Duplicate Key Insert Problem") in C. Mohan, `"Algorithms for
In the PDF that I looked at, section 3.1.1 is
3.1.1. Duplicate-Key-Insert Problem
if it matters.
> Creating Indexes for Very Large Tables Without Quiescing Updates"
> <https://dl.acm.org/doi/10.1145/130283.130337>`_, 1992.
> @@ -4179,7 +4179,7 @@ When the exchange is initiated, the sequence of operations is as follows:
> This will be discussed in more detail in subsequent sections.
>
> If the filesystem goes down in the middle of an operation, log recovery will
> -find the most recent unfinished maping exchange log intent item and restart
> +find the most recent unfinished mapping exchange log intent item and restart
> from there.
> This is how atomic file mapping exchanges guarantees that an outside observer
> will either see the old broken structure or the new one, and never a mismash of
thanks.
--
~Randy
next prev parent reply other threads:[~2025-08-21 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 13:13 [PATCH] Documentation/filesystems/xfs: Fix typo error Alperen Aksu
2025-08-21 16:54 ` Randy Dunlap [this message]
2025-08-29 22:26 ` Jonathan Corbet
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=70c48801-83fe-413f-8a8e-5db71c8d1c8d@infradead.org \
--to=rdunlap@infradead.org \
--cc=aksulperen@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-xfs@vger.kernel.org \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).