public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: sawara04.o@gmail.com, clm@fb.com, josef@toxicpanda.com, dsterba@suse.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs: Fix incorrect log message related barrier
Date: Wed, 21 May 2025 13:45:15 +0930	[thread overview]
Message-ID: <e508301e-4474-4490-93ad-bbea3e6ed04d@gmx.com> (raw)
In-Reply-To: <20250521032713.7552-3-sawara04.o@gmail.com>



在 2025/5/21 12:57, sawara04.o@gmail.com 写道:
> From: Kyoji Ogasawara <sawara04.o@gmail.com>
> 
> Fix a wrong log message that appears when the "nobarrier" mount
> option is unset.
> When "nobarrier" is unset, barrier is actually enabled. However,
> the log incorrectly stated "turning off barriers".
> 
> Signed-off-by: Kyoji Ogasawara <sawara04.o@gmail.com>

Reviewed-by: Qu Wenruo <wqu@suse.com>

This is definitely a copy-paste-error.

And we can add a fixes tag when merging:

Fixes: eddb1a433f26 ("btrfs: add reconfigure callback for fs_context")

Thanks,
Qu

> ---
>   fs/btrfs/super.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
> index 012b63a07ab1..0e8e978519d8 100644
> --- a/fs/btrfs/super.c
> +++ b/fs/btrfs/super.c
> @@ -1462,7 +1462,7 @@ static void btrfs_emit_options(struct btrfs_fs_info *info,
>   	btrfs_info_if_unset(info, old, NODATACOW, "setting datacow");
>   	btrfs_info_if_unset(info, old, SSD, "not using ssd optimizations");
>   	btrfs_info_if_unset(info, old, SSD_SPREAD, "not using spread ssd allocation scheme");
> -	btrfs_info_if_unset(info, old, NOBARRIER, "turning off barriers");
> +	btrfs_info_if_unset(info, old, NOBARRIER, "turning on barriers");
>   	btrfs_info_if_unset(info, old, NOTREELOG, "enabling tree log");
>   	btrfs_info_if_unset(info, old, SPACE_CACHE, "disabling disk space caching");
>   	btrfs_info_if_unset(info, old, FREE_SPACE_TREE, "disabling free space tree");


  reply	other threads:[~2025-05-21  4:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21  3:27 [PATCH 0/2] btrfs: Improve logging for barrier-related operation sawara04.o
2025-05-21  3:27 ` [PATCH 1/2] btrfs: Raise nobarrier log level to warn sawara04.o
2025-05-21  4:13   ` Qu Wenruo
2025-05-24  2:21     ` Kyoji Ogasawara
2025-05-24  3:48       ` Qu Wenruo
2025-05-25  2:32         ` Kyoji Ogasawara
2025-05-25 17:45           ` Kyoji Ogasawara
2025-05-26  4:54             ` Qu Wenruo
2025-05-26  9:21               ` David Sterba
2025-06-11 17:06                 ` Kyoji Ogasawara
2025-05-26  9:14         ` David Sterba
2025-05-21  3:27 ` [PATCH 2/2] btrfs: Fix incorrect log message related barrier sawara04.o
2025-05-21  4:15   ` Qu Wenruo [this message]
2025-05-24  2:00     ` Kyoji Ogasawara
2025-05-24  2:09       ` Qu Wenruo
2025-07-21  8:07         ` Kyoji Ogasawara

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=e508301e-4474-4490-93ad-bbea3e6ed04d@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sawara04.o@gmail.com \
    /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