public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: sawara04.o@gmail.com
To: clm@fb.com, josef@toxicpanda.com, dsterba@suse.com
Cc: Kyoji Ogasawara <sawara04.o@gmail.com>, linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: Improve logging for barrier-related operation
Date: Wed, 21 May 2025 12:27:09 +0900	[thread overview]
Message-ID: <20250521032713.7552-1-sawara04.o@gmail.com> (raw)

From: Kyoji Ogasawara <sawara04.o@gmail.com>

This patch series improves logging related to barrier operations.

The first patch raises the log level for the "nobarrier" to better
reflect the associated risk.

The second patch fixes an incorrect log message that could cause
confusion.

Kyoji Ogasawara (2):
  btrfs: Raise nobarrier log level to warn
  btrfs: Fix incorrect log message related barrier

 fs/btrfs/super.c | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-05-21  3:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21  3:27 sawara04.o [this message]
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
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=20250521032713.7552-1-sawara04.o@gmail.com \
    --to=sawara04.o@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.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